Skip to main content

Advanced

The Advanced alarm rule template provides monitoring capabilities by allowing you to create complex alarm conditions using multiple variables, related entities, and custom expressions.

advance2.png

Configuration

Advanced Rules allow you to define complex alarm logic by combining multiple metrics, properties, related entities, and thresholds using AND/OR conditions. This enables precise monitoring and reduces false positives.

Define Basic Rule Details

new_rule.png

  1. Navigate to New Rule>Advanced.

  2. In Rule Name, enter a descriptive name for your advanced rule.

  3. Add a Description to explain the purpose of the rule.

  4. Under Target Entity, select the entity type to monitor.

  5. Click Apply Filters to limit the rule to specific entities based on attributes.

Define Variables

Variables represent the metrics or properties used in rule evaluation.

new_rule_variable.png

  1. In the Variables section, click Add Variable.

  2. Choose the variable type: Property, or Metric.

  3. Assign each variable a label. (example, PV1: Property → Overall Status).

  4. (Optional): Select Select Related Entities to define variables. Choose the topology and related entity type.

Configure Rule Expression and Conditions

rule_expression.png

  1. Under Rule Expression and Conditions, select Expression Builder.

  2. Define one or more Threshold Groups.

    Why Use Threshold Groups?

    Threshold groups allow you to define multiple independent conditions that can trigger an alarm.

    • Monitor multiple conditions within a single rule.

    • Trigger an alarm when any one set of conditions is met.

    • Assign severity based on the condition that occurs.

    threshould.png

  3. How Threshold Groups Work:

    • All conditions within a group must be met (AND).

    • Any group can trigger the alarm (OR).

    • The group that triggers the alarm determines the severity.

  4. Define Threshold Criteria.

    1. Select a variable (PV or RV).

    2. Choose an operator (for example, above, equals, not equals).

    3. Enter the threshold value.

    4. Set the Severity for alarms triggered by this group (for example, Critical).

    5. Select the Window duration (for example, 5 minutes).

    6. Click Save to activate the Advanced Rule.

  5. Configure notifications.

    You can set up a notification plan for the alarm rule to notify users when the alarm is triggered.To add users to the notification plan, click the Add box and check the users to be added. You can also use an email distribution list for the notification plan.

    Note

    Available users are determined by the users listed in the LDAP and User Management sections of the Settings tab.

  6. Choose Action.

    You can choose a default action, which might be predefined in your system. Alternatively, you can select actions such as sending notifications through Webex, Teams, Slack, or other integrated platforms.

  7. Save Rule: Once you have configured all the necessary parameters, click "Save" to create your new alarm rule

Note

Make sure the UI property com.vi.ui.property.alarm is set to true for Advanced Rules to function correctly.

Advanced Rule – Supported Scenarios

Advanced rules allow you to create alarms using metrics, properties, and filters for a single entity. The following scenarios are supported when using the Expression Builder.

Single Entity – Single Metric

Create an alarm based on a single metric value.

  • Entity: ESXHost

  • Input: CPU Utilization (Metric)

  • Condition: CPU Utilization > 1

Single Entity – Single Property

Create an alarm based on a property value.

  • Entity: ESXHost

  • Input: Overall Status (Property) Condition

  • Overall Status = Green

Single Entity – Metric and Property

Create an alarm using a combination of a metric and a property.

  • Entity: ESXHost

  • Inputs: CPU Utilization, Overall Status

  • Condition: CPU Utilization > 1 OR Overall Status = Green

Single Entity – Multiple Metrics

Create an alarm using multiple metrics.

  • Entity: ESXHost Inputs: CPU Utilization, Avg VM CPU Ready % Condition: CPU Utilization > 1 OR Avg VM CPU Ready % > 1

  • Inputs: CPU Utilization, Avg VM CPU Ready %

  • Condition: CPU Utilization >1 OR Avg VM CPU Ready >1

Enabling the New Alarms Engine

Prerequisites

  • Access to Settings > Service Management.

  • Required permissions to update service properties

Procedure

Step 1: Enable the Alarms Engine in UI Service

  • Navigate to Settings>Service Management.

  • Search for UI Service.

  • Add the following property: com.vi.ui.property.alarm: true

Enabling the New Alarms Engine to Process Existing Templates

To migrate supported alarm templates from the existing alarms service to the new Alarms Engine, complete the following steps.

Step 1: Enable the New Alarms Engine

  1. Navigate to Settings> Service Management.

  2. Search for Alarm Service and add the following property:

    com.vi.alarms.engine.enabled = true

Step 2: Disable Supported Templates in the Existing Alarms Service

To avoid duplicate alarm evaluation, disable the templates that will be processed by the new engine.

  1. In the Alarm Service, set the following property:

    com.vi.alarms.disabled.templates = template1, template2

    This property specifies the list of alarm templates that should be disabled in the existing alarms service.

Step 3: Enable Template Processing in the New Alarms Engine

  1. Navigate to Settings >Service Management.

  2. Search for vw-alarms-mde service and set the following property:

    alarms.engine.templates.enabled = template1, template2

This property enables the new Alarms Engine to process the specified templates. The list of supported templates is the same as those listed in Step 2.

By default, the new Alarms Engine supports the following templates:

  • PropertyAlarm - advance

  • GenericAlarm- advance

In this section: