# Alert Configuration

Use the Alert Configuration tab to specify which actions should generate an alert in the Dashboard. Only users with Administrator privileges can view this page. See the following sections for explanations of actions that can be performed in this tab:

| • | Enable Alerts

| • | Critical Alerts

| • | Important Alerts

Enable Alerts

Alerts are classified into two categories: Critical and Important. These classifications cannot be changed. You have the option of choosing which actions will generate alerts on the Dashboard.

To enable any specific alert type:

| 1. | Select the Send Alert to Dashboard check box. When an Alert is triggered, the Dashboard page displays the Alert in the Alerts section.

| 2. | Click Save.

Alerts related to Activatable licenses are tested and triggered at 5-minute intervals. Alerts related to Concurrent licenses are tested and triggered at one-minute intervals. Any triggered alert will only be displayed on the Dashboard page when that page is reloaded or refreshed.

Critical Alerts

| • | Vendor daemon down: Triggers an alert when either the license server manager (lmadmin) or any vendor daemon stops running. This alert is triggered when these processes stop, regardless of the intention (either unexpectedly because of an error or purposely by a license administrator).

| • | Out of activatable licenses: Triggers an alert when the number of available activatable licenses is zero (0) for a product (identified using the feature or feature set name) and version. This indicates that all activatable licenses for the product have been issued.

| • | Out of overdraft licenses: Triggers an alert when there are no remaining overdraft licenses for a product (identified using the feature or feature set name) and version. This means that the license server issued all overdraft licenses.

| • | Activatable license expired: Triggers an alert when an activatable license for a product (identified using the feature name) and version expires.

| • | Out of concurrent licenses: Triggers an alert when all concurrent licenses have been checked out for a feature.

| • | Concurrent license expired: Triggers an alert when a concurrent license for a feature expires.

| • | Date-based version expired: Triggers an alert when the Feature Version expiration date has passed. If you enable this alert, you must also set the Enable Date-based Versions check box (under the Vendor Daemon Configuration tab). The software publisher will let you know if you need to configure these properties. The Feature Version value must be specified properly for this alert to be activated.

Important Alerts

| • | Activatable threshold exceeded: Triggers an alert when the enterprise uses the specified percentage of total a3ctivatable licenses for a product (identified using the feature name) and version. You must specify the percentage of the total activatable licenses that, when reached, triggers an alert. (The percentage can be up to 100%).

| • | Overdraft license issued: Triggers an alert when the license server issues an overdraft license for a product (identified using the feature name) and version.

| • | Activatable license expiring: Triggers an alert N number of days before an activatable license expires. You specify the number of days (N) advanced notice you want (N may be up to 3 digits in length).

| • | Concurrent threshold exceeded: Triggers an alert when the specified percentage of the total concurrent licenses have been issued. You specify the percentage that, when reached, triggers an alert (The percentage can be up to 100%).

| • | Concurrent license expiring: Triggers an alert N number of days before a concurrent license expires. You specify the number of days (N) advance notice you want (N may be up to 3 digits in length).

| • | Date-based version expiring: Triggers an alert N number of days before the Feature Version date (N may be up to 3 digits in length)). If you enable this alert, you must also set the Enable Date-based Versions checkbox (under the Vendor Daemon Configuration tab). The software publisher will let you know if you need to configure these properties. The Feature Version value must be specified properly for this alert to be activated.

FlexNet Publisher

2022 R2

Alert Configuration

Open topic with navigation