Define an Alert for a Resource Group

Available only in vFabric Hyperic

This page explains how to define an alert for a compatible group - a group whose members are all of the same resource type.

Understanding Resource Group Alerts

A resource group alert is an alert assigned to a compatible group - a group or resources you have defined that contains selected resources, all of which have the same resource type.

Resource group alerts are different that resource alerts in these ways:

  • A resource group alert definition has a single condition - A resource group alert definition is based on a single condition.

  • A resource group alert condition is based on the behavior of multiple resources - Resource group alerts are evaluated differently than other HQ alert types. A resource alert or resource type alert is fired for a specific resource based on monitoring results for that resource only.  A resource group alert fires when a metric condition is true for a specified number or percentage of the resources in the group.

  • The only action a resource group alert can trigger is an escalation - The only action you can assign to a group alert definition is an escalation.

  • A resource group alert fixes itself - Although you can mark a group alert fixed - from the group's Alerts tab or other alert views - you don't need to. HQ automatically marks a group alert "fixed" when the condition that caused it to fire is no longer true. This shows up in the UI as "The problem fixed itself." in the "Alert Detail" screen.

Define a Resource Group Alert

Step 1 - Select Target Compatible Group

  1. Browse to the compatible group to which the new alert definition will apply.

  2. Click the Alert tab.

  3. Click Configure.

  4. Click New to display the New Alert page.

Step 2 - Define Alert Properties

On the New Alert page, define each property in the "Alert Properties" section. 

  • Name — Name assigned by the user creating an alert definition. A fired alert is identified, in the Hyperic user interface and alert notifications, by the alert definition name and a timestamp. An alert definition name should clearly communicate the nature of the problem. For example, "Down" for an alert on availability, or "Low Memory" for an alert on free memory.

  • Description — Description entered by the user creating the alert definition.

  • Priority — The severity of the problem, as defined by the person creating the alert definition: "Low", "Medium", or "High". A consistent policy for defining an alert definition priority makes it easier to triage problems appropriately. An alert's priority is shown in Hyperic pages that present alert status and in alert notifications. You can sort alerts by priority in vFabric Hyperic's Alert Center or Operations Center.

  • Active — The current enabled/disabled status of the alert definition. Alerts only fire for enabled alert definitions. When an alert definition is disabled, Hyperic does not evaluate its condition or fire alerts for it.

Step 3 - Define Alert Condition

Determine why the alert will fire.

  1. Select how many (an absolute number or percentage) of the resources in the group (the number of members is shown) that must satisfy the condition.

  2. Select the metric and the comparison value that those resources must satisfy.

  3. Click OK when you are done. 

Step 4 - Assign Escalation Action

Assign an escalation to the alert. The series of notifications defined in the escalation  will be performed when an alert is fired. You must define an escalation before you can assign it to an alert definition. Click Escalation Schemes Configuration on the Administration tab to define an escalation.