Home
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.
Basic Operations and Setup (Admin Only)
This section is organized into a series of instructions designed to guide you through the beginning steps of setting up your Monitor system.
Parse a Debug Log
Manually Parse a Debug Log

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.
- Document Organization
  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.
- Theory of Operation
  Monitor monitors tools with licenses using live sampling and debug logs for denials, and it monitors tools with no licenses using wrapper scrips and a monitoring agent.
- Components
  All Altair Accelerator software products are based on a client/server architecture and have three main components: a server, daemons and taskers.
- Installation
  There are four different types of installations available for Monitor.
- First Steps
  We suggest as first steps that you check Monitor to be sure it’s running properly and then perform a few basic tasks to get a feel for the system.
- Common Questions and Basic Uses
  This section explains how to use Monitor to answer common questions. In most cases, there isn’t one answer to a question. Some investigation is required.
- Using the Graphical User Interface
  Monitor has many views and reports, and this section details all of them. It is designed as a reference, so when you generate a report, you will understand all its parameters.
- Basic Operations and Setup (Admin Only)
  This section is organized into a series of instructions designed to guide you through the beginning steps of setting up your Monitor system.
- Troubleshooting
  Answers to common questions when using Monitor.
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

View All Altair Accelerator Help

Manually Parse a Debug Log

If the debug log environment is not suitable for live monitoring, logs can be manually parsed using the appropriate parsing command for each license manager type:

FlexNet Publisher debug logs
DSLS™ debug logs
Altium™ debug logs

This section describes how to enable FlexNet Publisher debug logs using a static or a daily rotating debug log. We recommend using a daily rotating log.

This process takes several steps.

Static Debug Logs

A static debug log is one that captures both the lmgrd and vendor daemon output. The lmgrd daemon contributes date stamps, while the vendor daemon contributes all license activity. (lmgrd is the FlexNet Publisher daemon, which allows Monitor to gather data.) At license server startup time, pass the -l </path/to/debug/log> option to lmgrd. This will create a debug log that will contain all the information necessary for Monitor to properly analyze the log contents. However, this file is not rotatable, and it will require a restart of the server to rotate the log. This type of log will also grow over time, the rate at which is determined by the amount of activity on the license server. Hence, we recommend you use the daily rotating debug log.

Rotating Debug Logs (Recommended)

A rotating debug log is one that captures only the vendor daemon output, which means there will be no date stamps in the file. Because of this, there is a chance for inaccurate assumptions in the log. For example, if license activity ceases for more than 24 hours, the day will become unknown due to there not being a visible roll-over at midnight.

To address this, the log must be rotated daily, typically a few minutes after midnight. This ensures that the license activity is current for n 24-hour period and will keep the file size small. Monitor will need to be configured to automatically look for a daily log file. For this to work properly, the debug log must be rotated to a file with a name reflecting the current date, in the format of <fileName>.<YYYYMMDD>, using the lmswitch command in conjunction with a task scheduling facility.