Denial Reports

Monitor tracks denials, as reported by the license manager. A denial is essentially a license request, which is denied.

The same filters and report by options are available in this page to help find the information desired, with the exception of project and version support. Project support is not available because the debug log contains historical data of its own; currently there is no historical mapping for projects in Monitor. Version support is not available because the debug log does not contain version information for denial events.

Figure 1.


Denial Statistics

This provides a snapshot of denials. If it shows a high number of denial you may need to add more licenses; if there are no denials you may have too many.

Figure 2.


The Denial Statistics page is identical to the Checkout Statistics page with the exception that it shows statistical information about denial events. The same filters and report-by options are available to help you find the desired information, with the exception of project and version support. Project support is not available because the debug log contains historical data of its own; currently there is no historical mapping for projects in Altair Monitor. Version support is not available because the debug log does not contain version information for denial events. The Denial Statistics report shows the number of denials detected and the number of unique users that experienced denials, the timing of the latest denial, and provides links to the plot and heatmap pages for visualization of the report. The Denial Statistics Report includes the following columns:

The Denial Statistics Report includes the following columns:
Tag
The tag representing the license server.
Feature
The license feature name.
Denials
The number of denials.
Users
The number of users.
Latest
The last recorded time of a denial.
Graphs
The links to the detailed plot page, the statistical plot page, the efficiency histogram page, and the activity heatmap report.

Detailed View

This table shows the reason for denials, which enables you gain insight about your license management utilization.

Reasons are taken exactly as they are found from the data source. If no reason is provided, the reason will be unknown. The reason can be used to filter the denial reports to determine the root cause of denials. For example, a denial that is caused by a lack of capacity will most likely hold a different weight than a denial that is caused by a self-imposed limit that is defined in the license manager options file.

In this example, the reason was “timeout from vendor queuing” that means the request took too long. You would need to evaluate that and determine your actions based on your unique license needs.

Figure 3. Denial Details Report


The Denial Details Report shows the actual denials that are the basis of the statistics shown in the statistics view. This report shows all the information that is normally found in a debug log denial record. The denial details report also displays columns for custom group types that have been configured. The group shown indicated the group that the user was a member of at the time of the denial.

The report can be sorted using the same filtering techniques available in the statistics view.

About Denial Reasons

Monitor tracks the reasons for denials, as reported by the license manager, if applicable. Currently, only FlexNet Publisher provides denial reasons via the debug log. Reasons are taken exactly as they are found in from the data source. If no reason is provided, the reason will be "unknown".

The reason can be used to filter the denial reports to determine the root cause of denials. For example, a denial that is caused by a lack of capacity will most likely hold a different weight than a denial that is caused by a self-imposed limit that is defined in the license manager options file.