OpenLM Alerts

Overview

OpenLM Alerts helps you proactively monitor your licensing environment by defining custom rules that initiate notifications when specific conditions are met. It enhances system stability, ensures compliance, and minimizes downtime by alerting administrators to potential issues like license server outages, usage spikes, and license expirations.

Alerts consist of 3 components:

• Alert rules: Define conditions that prompt an alert.
• Alert log (Alerts tab): View all activated alerts.
• Notification service: Configure how alerts are delivered (email, ticket, etc).

Tip: Use alerts to transition from reactive troubleshooting to proactive system health monitoring.

Alerts tab

Alerts tab displays all triggered alerts across OpenLM services.

What you can do:

• View alert messages generated by the system.
• Filter by time, source, or severity (e.g., Critical, Warning, Info).
• Select an alert to view its full description, origin, and time.

This view gives a snapshot of current or past issues in your environment, such as licensing denials or memory errors like "Java heap space".

Alert rules tab

In the Alert Rules tab, you define and manage the logic for alerts.

What you can do:

• View existing rules by name and severity.
• Activate or deactivate rules using toggle switches.
• Filter and search the rule list.
• Add new rules using custom conditions.

Defining a rule:

1. Select Add Rule.
2. Set conditions severity: waring, alert, notice, system.
3. Select the service to be alerted about:
   • Dongle Monitoring
   • Projects Service
   • Directory Synchronization Service
   • Feature Service
   • Subscription Optimizer
   • OpenLM Server
   • Reporting Service
   • User Availability Service
4. Assign a rule name.
5. Click SAVE.

Note: Rules determine when an alert is triggered. Notifications define how and who is informed.

System events tab

The System Events tab logs detailed system activity across OpenLM components.

What you can do:

• View logs including service status changes, warnings, or errors.
• Filter by time, severity, or service name.
• Investigate root causes for triggered alerts.

This section complements the Alerts tab by providing insight into the source of issues.

Notification service

Use the Notification Service to manage how alerts are delivered.

Supported channels:

• Email notifications: Configure sender details, recipients, and security settings.
• Ticketing system integration: Create incident tickets using email or direct integration with platforms like ServiceNow.

Steps to configure:

1. Navigate to Notifications Service in the sidebar.
2. Enable/disable notification methods (email or ticket).
3. Add recipients or endpoint details.
4. Send a test notification to confirm setup.

Recommendation: Always validate your configuration with a test alert.

Additional best practices

• Review and refine alert rules regularly based on evolving licensing needs.
• Assign severity levels appropriately to prioritize actions.
• Use system events for post-mortem diagnostics and trend spotting.
• Combine Alerts with Compliance and Notifications modules for full observability.