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
- License Server Management
- Other Configurations
- Command Line Operations
- Reference
  - Troubleshooting
    Before troubleshooting Monitor, it is recommended that you make yourself familiar with its theory of operation.
  - Performance Tuning
    Monitor is designed to be a highly efficient and scalable application. However, in larger enterprises, certain factors may affect the performance of the system as a whole.
  - Data Files
  - Configuration Commands
  - Autostart Directory
    With the command vovautostart, on vovserver startup, scripts can be specified to execute automatically.
  - Data Collection Commands
  - Database Loading Commands
  - Maintenance Tasks
    Maintenance tasks are managed via the Configuration Information page. Jobs for these tasks are displayed in the periodic job list page.
  - Accuracy
    This section describes the accuracy of the Monitor sampling methodology with respect to monitoring live servers for checkout and checkin information.
  - Access Control List
    An Access Control List (ACL) is a list of permissions that are attached to an object. The list defines who can access the object (an agent) and what actions the agent can perform on the object.
  - Widgets
    A Monitor "widget" is a web page that generates various reports, but with no interface or visual aids. Widgets are called by other pages that provide these items, as well as details about the content provided by the widget, such as a title and description of the content.
  - Time Zones

View All Altair Accelerator Help

DSLS Log File

Usage

add_DSLS_LOG </path/to/log> -tag <TAG> [OPTIONS]

Options

</path/to/log>	The first argument must be a path to an CodeMeter™ log file. For a rotating log, the name specified must be in the form of <fileName>.@LATEST@.log. See Debug Log Monitoring for more details.
-tag <TAG>	Specify the TAG to identify the license server. The TAG may contain only alphanumeric characters and underscores (_). The use of upper case characters is recommended for style purposes.
-tz, -timezone	Set to timezone which was used to generate the debug log. Ex: PST8PDT. If debug log was generated in the same timezone as the Monitor server, leave blank.
-checkouts	Extract checkout information from debug log. This can be used to monitor checkouts that are shorter in duration than the sampling rate.
-host	If monitoring debug logs from triads, use this option to denote the server from which the data originates.
-minPeriod <TIMESPEC>	Minimum sampling period.
-maxPeriod <TIMESPEC>	Maximum sampling period.
-autokill <TIMESPEC>	Kill parsing job after specified time.
-usekeystore	Use DSLS key store file ($SWD/vovlmd/TAGNAME.ks) for authentication.
-robust	Warn and ignore unparsable license usage output lines.