Joint Debug Log Monitoring (FlexNet Publisher only)

Web-based Configuration

The form in the monitor administration web page contains a field for specifying the path to a single debug log for FlexNet Publisher servers being configured. When multiple debug logs exist for a single tag, the file-based stand-alone configuration must be used (see below).


Figure 1. Joint Monitoring

Optionally, checkout information can be acquired in addition to denial information by checking the box for this functionality. This feature is currently considered experimental as Altair Accelerator continues to improve the handling of corrupt and incomplete data commonly encountered with debug logs.

File-based Configuration

In the add_LM_LICENSE_FILE configuration procedure, the -debuglog option allows for a file path to be specified that will create a debuglog parsing job that will run for the tag specified in the configuration, in addition to the sampling job. When multiple debug logs exist for a single tag, the file-based stand-alone configuration must be used.

Optionally, checkout information can be acquired in addition to denial information by adding the -debuglogcheckouts option. This feature is currently considered experimental as Altair Accelerator continues to improve the handling of corrupt and incomplete data commonly encountered in debug logs.