Current Limitation
The SolarWinds Platform currently requires administrators to assign a fixed severity (Notice, Informational, Warning, Serious, or Critical) within the Alert Properties section of an alert definition.
Although the Trigger Condition configuration supports multiple conditions using AND/OR logic, there is no native method to dynamically assign the alert's severity based on which trigger condition is satisfied.
This requires administrators to create multiple alert definitions for different severity levels or maintain a single alert with a fixed severity that may not accurately represent the current operational condition.
Proposed Enhancement
Introduce a Dynamic Severity option within the Alert Properties configuration.
Administrators should be able to choose between:
- Static Severity: Retain the existing functionality of selecting one severity for the entire alert definition.
- Dynamic Severity: Assign an alert severity based on the specific condition or condition group that triggers the alert.
For example:
- IF source severity = Error, assign Warning.
- OR IF source severity = Serious, assign Serious.
- OR IF source severity = Critical, assign Critical.
The feature should also support metric-based conditions, such as CPU utilization, disk capacity, application component status, node availability, and interface performance.
Additional Functional Requirements
- Conditional Severity Mapping: Allow administrators to configure severity mappings directly within the Trigger Condition editor or a dedicated Severity Mapping section.
- Automatic Severity Escalation: Allow an active alert to transition from Warning to Serious or Critical when monitored conditions worsen.
- Automatic De-escalation: Allow severity to decrease when conditions improve, without unnecessarily resetting and recreating the alert.
- Multiple Matching Conditions: When multiple conditions are true, assign the highest applicable severity by default, with configurable precedence.
- Alert History: Maintain an audit trail of all severity changes, including timestamps and triggering conditions.
- Integration Support: Expose the dynamically assigned severity through supported APIs, webhooks, and alert action variables so external ITSM solutions can synchronize incident priorities.
- Existing Alert Compatibility: Preserve the current static severity configuration for existing alerts unless dynamic severity is explicitly enabled.
- Notification Controls: Allow administrators to trigger additional notifications when severity changes without creating duplicate incidents.
Business Justification
Dynamic severity would improve incident management by ensuring alert priority reflects the actual operational impact of the monitored condition.
This functionality would:
- Reduce duplicate alert definitions and administrative overhead.
- Minimize duplicate tickets in ITSM platforms.
- Improve consistency between SolarWinds severity levels and incident management priorities.
- Enable more accurate dashboards, operational reporting, and SLA tracking.
- Support standardized monitoring and escalation processes across enterprise environments.
Expected Outcome
A single SolarWinds alert definition should be capable of detecting multiple conditions, assigning the appropriate severity, and dynamically escalating or de-escalating an existing alert instance as operational conditions change.
This would provide more flexible, scalable, and maintainable alert management for enterprise SolarWinds environments.