Viewing and Configuring Alarms Globally through Alarm Templates

The purpose of Global Alarm Configuration is that you can associate thresholds and actions to Monitors/ Monitor Groups/ Monitor Types directly rather than from their individual screens. Additionally, you can view all the thresholds and actions associated with the attributes of a Monitor Type/ Monitor Group / Monitor on a single screen.

How to Demos: View our demo on configuring Alarms on our website.

You can perform the following functions in the screen:

• Create and associate a threshold for an attribute by clicking 'Associate' link. It opens the 'Configure Alarms' page, herein you can create a new threshold or apply an existing threshold for the attribute.
• Edit already existing thresholds by clicking on the threshold name.
• Configure Alarms for:
  • Monitors
  • Monitor Groups
  • Monitor Types

Monitors

• Select the Monitor Type from the list.
• Select the specific Monitor for which you want to configure alarms.
• Select from the list of attributes given and associate thresholds.

Monitor Groups

• Select the Monitor Group from the list.
• Select Action Type: Individual or Template.
• For Individual:
  • Select the desired attributes listed for each Monitor and associate thresholds.
• For Template:
  • Select Monitor Type.
  • Select from the list of attributes given and associate thresholds.
  • For information about "Override existing Threshold Configuration" option, see below.

Monitor Types

• Select the Monitor Type from the list.
• Select from the list of attributes given and associate thresholds.
• For information about "Override existing Threshold Configuration" option, see below.

Known Limitations

• Overriding existing Threshold Configuration:

  For Monitor Groups and Monitor Types, while associating thresholds, an option Override existing Threshold Configuration is displayed. Enabling this option will override all the existing thresholds/actions with the recently configured ones in Individual, Monitor Group, and Monitor Type alarm templates. If left unchecked, the existing threshold configuration of the Monitor(s) is maintained and the new threshold configurations are applied only to the remaining monitors.

• Monitor Group templates are given priority over Monitor Type templates.
  For example:
  • If a monitor belongs to a Monitor Group and both the Monitor Group and Monitor Type templates have threshold configurations, the Monitor Group template will take precedence.
  • If a monitor previously had a Monitor Type template applied and is later associated with a Monitor Group that has a Group template, the Group template’s thresholds/actions will override the earlier Type template.
• Configuring thresholds when a monitor belongs to two Monitor Groups. It is not recommended to configure two different thresholds for the same attribute in two different groups. This will result in an error.
• If a monitor belongs to two Monitor Groups with different thresholds/actions for the same attribute, the configuration of the group template that was applied first will be retained.
• Different Actions for various severities configured at the Monitor / Monitor Type / Monitor Group levels cannot be merged together. Only one level’s action-severity configuration will be applied.
• As a best practice, use separate thresholds/actions for Monitor Group or Monitor Type templates, and different ones for Monitor-level configuration.
• Consecutive Polls in Alarm Template: Avoid configuring only the Consecutive Poll option in Alarm Templates without associating any actions.
• If an Alarm Template contains only the Consecutive Poll setting and no actions, performing Delete and Disassociate will not remove the consecutive poll configuration from the monitor.
• Anomaly profiles cannot be created or associated via Monitor Group or Monitor Type templates. They must be configured individually at the monitor level.
• Attribute Dependencies in Alarm Templates:
  • Dependency configuration settings for individual monitors are not available in the Central Server.
  • When a Central template is applied, configuring a template in a Probe for the same Monitor Type, Group, or individual Monitor may result in unpredictable behavior.
  • When both action and dependency configurations are applied, dependency configuration will apply only to the resources where the action configuration is applied.
  • Delete and Disassociate is the only method to delete a template and revert to default settings. Saving a template with default settings is still treated as a valid template and will be applied.
  • When multiple Monitor Group templates exist, the group with the lowest Group ID takes precedence.
  • If a monitor is disassociated from a Monitor Group in the Central Server, all template configurations for that monitor are removed. Even if the monitor qualifies for another applicable template, it will not be auto-applied.
  • When a monitor is added from the Central Server and associated with a group at creation time, the Monitor Group template will not be applied. Only the Monitor Type template will apply.
  • When a Monitor Group template is created in Central, it syncs to all relevant Probes. However, if the group is deleted in Central, the template will be deleted in the Probe only if that group contains at least one monitor from that Probe.
  • The Central and Probe servers may have different template configurations for the same Monitor Type. However, performing Delete Template or Delete and Disassociate from Central will remove that template configuration from both Central and Probes.
  • If a template is created in Central for a Probe’s Monitor Group, it syncs to the Probe. However, if the Group Template is later updated in the Probe, those updates will not sync back to Central.
  • When a dependency template is applied from Central, it will be enforced regardless of the Probe’s existing dependency configurations.

For more information, refer to the Associating Threshold and Action with Attributes section.