Create Report Configuration: Filter Properties
The Filter Properties page enables you to create filters to limit the data that is shown in a report. For example, you may want your report to show only usage information for feature f3, so you would create a filter to limit the data to only usage of that feature.
See Filtering Report Data for more information about creating report filters.
To specify filter properties:
| 1. | Select a report filter category from the Category list. |
| 2. | From the Operator list, select an operator symbol. |
| 3. | In the Event Filter field, type the value that for which you want to filter. |
| 4. | To add another filter, click Add New Filter and repeat steps 1 through 3. |
| 5. | For Raw and Usage Summary reports: In the Event Types section, specify which event types you want to appear in the report. |
|
Event Type |
Description |
||||||
|
Used |
A Used event consists of a license checkout/checkin pair. The number of Used events is summed over the time period of a report, and the duration that licenses are used is displayed in a report. License usage is calculated as the time between a checkout and its checkin. |
||||||
|
Queued |
A Queued event consists of a queue/dequeue pair. The number of Queued events is summed over the time period of a report, but the duration a license request is queued before being denied or granted is not displayed (however, queued duration can be calculated from data in a Raw report). If an application is configured for queuing and none of its licenses are available, a Denied event and a Queued event are written into the report log with the same timestamp. The application will continue to try to gain a license until one becomes available. Additional denials are not written for each try while queued or if a license is never granted. A queued request will remain queued until it is granted unless the vendor daemon goes down, the license server is shut down, or the request is canceled or timed out. |
||||||
|
Denied |
The number of denial events is summed over the time period of a report. A denial is instantaneous and has no duration associated with it. The why field in a Raw report gives the reason why a denial occurred. If filtering “false” denials is enabled, the report includes the number and percentage of “false” denials that were eliminated. |
||||||
|
Exceptions |
Exception (unsupported) events are generated when the license server receives a request for a feature it does not know about. Exceptions usually occur when the application and the license server are looking at two different license files. The application reads its license file and thinks it can get a license for the feature, but when it asks the license server for a license, the license server denies the request and logs it as an exception. The most common instances of exceptions are:
|
| 6. | For Peak Usage and Denial, Raw, and Usage Summary reports, specify how you want to handle spurious (or “false”) denials. See the topic, How Are Denials Analyzed?, for more information. |
| • | In the Time interval box, specify a number of seconds. During this time, denials for the same feature, user, host, process id, and report log file that occur in clusters are qualified for denial. |
| 7. | Click Next. |
See Also