Home
Altair Monitor Administrator Guide
Configuring Monitoring
Debug Log Monitoring
License utilization data that Monitor gathers primarily comes from license management tool's status command (e.g. the FlexNet Publisher lmstat command).
Stand-Alone Debug Log Monitoring
There may be situations where a debug log will need to be parsed in a stand-alone fashion as opposed to directly coupling it to a sampling configuration. In most cases, this will be any time there are multiple debug logs for the same tag.

Welcome
What's New
View new features for Monitor 2025.1.0.
Monitor Overview
A real time software license monitoring and management tool.
Monitor Tutorials
Currently there are no Monitor tutorials available.
Getting Started Guide
This manual describes the web user interface and provides instructions on common uses and best practices for users. It also provides the basic setup, installation and management practices for administrators. For both administrators and users, it functions as a getting started guide.
Altair Monitor User Guide
Altair Monitor is a software license tracking tool that reports current and historical license utilization. The license managers that Monitor supports includes FlexNet Publisher, Reprise, LUM, and many others. The primary user interface for accessing Monitor is a web interface.
Altair Monitor Administrator Guide
- Altair Monitor Overview
  This document describes how to configure and manage Altair Monitor.
- Enable CLI Access on UNIX
  This section explains how to set up a UNIX user's shell environment to have a proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
- Enable CLI Access on Windows
  This section explains how to set up a Window user's command prompt environment to have the proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
- Use Monitor Help
  Monitor documentation is available in HTML and PDF format.
- Server Operation
- Failover Server Candidates
  If a server crashes suddenly, VOV has the capability to start a replacement server on a pre-selected host. This capability requires that the pre-selected host is configured as a failover server.
- Daemon Operation
  Although the Monitor daemons are started automatically upon startup, there may be times where a daemon should be restarted. This section describes how to control the Monitor daemons.
- Daemon Manager Utility
  Although the Monitor daemons are started automatically upon startup, there may be times where a daemon should be restarted. This section describes how to control the daemons from the command line (CLI).
- Database
  Monitor stores historical information about jobs in a relational database. As of version 2015.09, the database is fully integrated and managed as part of Monitor. This section provides an overview of the components that run and manage the database.
- Configuring Monitoring
  - General Monitoring Configuration
  - License Server Monitoring
    Each license server to be monitored must be identified in the Monitor configuration. This can be accomplished by using the Admin web page or by editing the vovlmd configuration file (licmon.swd/vovlmd/config.tcl). The web page maintains a separate configuration, so when using both methods, be careful to configure only one monitor for each tag to avoid configuration conflicts.
  - Debug Log Monitoring
    License utilization data that Monitor gathers primarily comes from license management tool's status command (e.g. the FlexNet Publisher lmstat command).
    - Enable FlexNet Publisher Debug Logs
      This section describes how to enable FlexNet Publisher debug logs. It is crucial to understand the differences found in the debug log based upon the enable method. These differences will dictate how Monitor will be configured to import data from the logs.
    - Joint Debug Log Monitoring (FlexNet Publisher only)
    - Stand-Alone Debug Log Monitoring
      There may be situations where a debug log will need to be parsed in a stand-alone fashion as opposed to directly coupling it to a sampling configuration. In most cases, this will be any time there are multiple debug logs for the same tag.
    - Debug Log Configuration
  - False Denial Filtering
    If denial monitoring has been enabled, historical denial reports will be available. Denials are obtained from the debug log of the license daemon and are filtered when parsed so that false denials are not loaded into the Monitor database and included in reports.
  - Multi-Site Support
    Companies with multiple sites may decide to implement Monitor at each site instead of monitoring remote license servers across the WAN. Monitor supports two methods of aggregating remote data to a "main" site.
  - Project and Group Management
    For reporting purposes, users can be grouped to keep track of projects, departments, or other organizational units.
  - Network Monitoring
    Monitor can also be configured to monitor hardware and process information. These functions are enabled by launching a monitoring agent on each of the hosts to be monitored.
  - Monitor Processes
    For tools that are not licensed, usage tracking can still be achieved.
  - Wrapping Unlicensed Tools
    The wrapping technique for monitoring unlicensed tools uses Monitor's built-in license management capability. This basic capability is activated by first creating a served license, then instructing the tool to either count its run as a checkout, or to request a license before being checked out, via a script or binary wrapper. Monitoring occurs automatically.
- License Server Management
- Other Configurations
- Command Line Operations
- Reference

Stand-Alone Debug Log Monitoring

There may be situations where a debug log will need to be parsed in a stand-alone fashion as opposed to directly coupling it to a sampling configuration. In most cases, this will be any time there are multiple debug logs for the same tag.

The following lists some of the situations that require a stand-alone debug log configuration:

FlexNet Publisher and DSLS triad configurations, where a debug log is generated for each server in the triad.
FlexNet Publisher multi-daemon license files, where a debug log is generated for each daemon found in the license file.
Secure areas where sampling is not permitted.
Altium and CodeMeter, since there is no status command to sample.

Unlike the joint monitoring configuration, the stand-alone configuration method allows for binding more than one debug log to any tag that is also being monitored for usage. This can be accomplished via file-based configuration only.