Define an Alert for a Resource Type

Available only in vFabric Hyperic

Define a Resource Type Alert

This page explains how to define an resource type alert. A resource type alert is applied to all resources of the specific type that currently exist and new resources of the type that get created in the future. Only HQ Administrators can create resource type alerts.

Step 1 - Select Target Resource Type

  1. Click Administration in the masthead.

  2. Click Monitoring Defaults in "HQ Server Settings" section of the page.

  3. On the HQ Monitoring Defaults Configuration page, click Edit Alerts for the resource type for which you want to define an alert. The Monitoring Defaults page will display any alert definitions already assigned to the alert.

  4. Click New to create a new alert definition.

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 Set

On the New Alert page, define the Condition Set, and click OK when you are done. 

Condition Set

An alert condition specifies a resource metric value or event that will initiate the alert firing process.

The condition types you can choose when you define a alert vary by resource type and Hyperic version. If a condition type is not supported by your version of Hyperic or is not valid for the target resource, it will not appear as an option.

To define a condition, choose one of the following condition types, and supply required parameter values.

  • Metric condition -  To base the alert on the value of a metric that Hyperic collects for the resource:

    1. Metric - Select a metric from the selector list.  Only currently enabled metrics are listed.  (If the metric you're looking for is not listed, see the note below.)

    2. Define the rule for evaluating the metric value.  You can:

      • Compare metric value to an absolute value. Select an operator: >(greater than), <(less than), =(equal to), or != (not equal to), and enter a metric value. If the metric value is a percentage, specify it as a float value. For example, enter .99 for 99%, 1.0 for 100%. Use a period (.) as a decimal separator, rather than a comma (,).

      • Compare metric value to its minimum, baseline, or maximum value * , in vFabric Hyperic only. Select an operator: >(greater than), <(less than), =(equal to), or != (not equal to), and choose "Min Value", "Baseline Value" or "Max Value". Baselining must be enabled. For more information, see Baselines.

      • Fire upon change in metric value.  Click value changes.

To Enable Collection of a Metric

If you want to base a metric condition on a metric that is not currently collected, you have to enable collection of that metric. To do so, update the metric collection settings for the resource type (choose Monitoring Defaults from the Administration tab), or for the specific resource (click Metrics on the Monitor tab for the resource).

  • Inventory Property Condition - To define a condition that is triggered when the value of an inventory property for resource changes, select an inventory property.  The pulldown contains only those inventory properties that are valid for the type of the resource to which the alert applies.

  • Control Action Condition - When you define an alert for a resource that supports control actions, you can define a condition that is triggered when a particular control action is performed. If desired, you can base the condition on a control action with a particular result status: "in progress", "completed", or "failed".  Pulldowns allow you to select a control action that the resource supports, and a result status if desired.

  • Events/Log Level Condition - To define a condition that is triggered by a log event, select a message severity level ("error", "warn", "info", "debug", "all") and optionally a match string. The condition is satisfied each time a message of the selected severity that contains the match string (if one was specified) is written to a log file that Hyperic is tracking. Log tracking must be enabled for the resource. To determine the log files that Hyperic monitors for the resource, see the Configuration Properties section of the resource's Inventory tab. The log files that Hyperic monitors for a resource are defined using the server.log_track.files property. For configuration instructions, see  see Set Up Log Tracking for a Resource.

  • Config Changed... Condition - This type of condition is triggered by a change to a configuration file that Hyperic is configured to monitor for the resource. To limit the condition to a single file, enter its filename in the "match filename" field.  If you don't specify a filename, a change to any file monitored will trigger the alert.  To determine the log files that Hyperic monitors for the resource, see the Configuration Properties section of the resource's Inventory tab. The files that Hyperic monitors for a resource are defined using the server.config_track.files property. The maximum length for filename entered is  25 characters.  For configuration instructions, see Set Up Configuration Tracking for a Resource.

Define Additional Conditions

Available only in vFabric Hyperic

In vFabric Hyperic, you can define up to three conditions for an alert. To add another condition, click Add Another Condition and specify whether both the new condition and the preceding one must be satisfied for the alert to be triggered ("AND") or only one must be satisfied ("OR").

Define Recovery Alert Behavior

Available only in vFabric Hyperic

To designate the alert you're defining as a recovery alert, select the primary alert definition from the pulldown.

A recovery alert condition should detect when the condition that fired the primary alert is no longer true. When a recovery alert fires, it marks the primary alert "Fixed", and the primary alert definition is re-enabled. The primary alert definition should be configured to Generate one alert and then disable alert definition until fixed, as described below. For more information, see Define a Recovery Alert for a Resource Alert.

Enable Action Filters

An action filter can be used to control alert firing and alert actions.

Disable an Alert Definition upon Firing

Click Generate one alert and then disable alert definition until fixed to disable the alert definition after firing and reenable it when the alert that triggered it is marked "Fixed".

This option eliminates redundant firing for the same problem. If you do not choose this option, the alert will fire repeatedly as long as the triggering condition is still true.  

In vFabric Enterprise this configuration option, used in conjunction with recovery alerts, automates the process of disabling and re-enabling an alert definition. Result: (1) no redundant alerts for the same problem, and (2) you don't have manually "fix" an alert triggered by a transient problem.

Step 4 - Define Alert Actions

You assign actions to an alert definition on the Alert Definition page, which appears when you save a new alert definition or edit an existing alert definition.

The Alert Definition page is similar to the New Alert page, with the addition of Edit controls in the "Alert Properties" and "Condition Set" sections, and tabs at the bottom of the page for defining alert actions.

You can specify multiple actions to be performed automatically when an alert fires. The types of actions available in the Alert Definition page vary based on: (1) the type of resource the alert applies to, (2) your version of Hyperic, and (3) whether you've configured Hyperic for the types of actions that must be enabled before you can use them, such as escalations, OpenNMS trap actions, and in vFabric Hyperic, SNMP notifications.

To define an alert action, select one of the tabs and supply the required information:

Control Action

Available only in vFabric Hyperic

In vFabric Hyperic, you can define a resource control action for Hyperic to perform when the alert fires. The control action can target the current resource (the one to which the alert definition is assigned) or a different resource on the same platform, as long as the resource type has Hyperic-supported control actions. To configure a control action for the alert, select the Control Action tab and click Edit. The Add Control Action page appears; click the thumbnail below for a screenshot. Follow the instructions on the associated help page. You can only assign a single control action to an alert definition. Note: You cannot assign a control action to a resource type alert.

images/download/attachments/79038211/AddControlAction.png

Notify HQ Users

Click Add to List on this tab to specify one or more Hyperic uses as notification recipients. On the user selection page, choose the users to be notified when the alert fires. The help page has instructions. 

Notify Other Recipients

Click Add to List on this tab to specify non-Hyperic user email recipients for alert notifications.  The help page has instructions. 

Script

Available only in vFabric Hyperic

In vFabric Hyperic, to assign a script action to the alert definition, click the Script tab, enter the full path to the script, and click Set.  Hyperic will run the script when the alert fires. Scripts can reference alert-related Hyperic environment variables to perform custom notification logic. For information, see Define a Script Action for an Alert.

Script actions are synchronous

Script actions execute one at a time. Until a script action completes, additional alerts will not fire on the resource.

OpenNMS

If Hyperic Server is configured for OpenNMS integration, you can use this tab to configure Hyperic to send an SNMP trap to OpenNMS when the alert fires. The notification will be generated by opennms_notify.gsp alert notification template.

To configure an OpenNMS trap action, enter:

  • Server - Listen address for the OpenNMS server

  • Port for the OpenNMS server.

For more information, see http://support.hyperic.com/display/hyperforge/HQU+OpenNMS.

SNMP Notification

Available only in vFabric Hyperic

If the Hyperic Server is configured to send SNMP notifications to your NMS, you can use this tab to configure a trap notification action. See SNMP Server Configuration Properties for more information.

The notification sent when the alert fires will contain three variable bindings:

  • sysUptimeOID.0 - No configuration is required for this binding.

  • snmpTrapOID.0 - This binding is configured on the HQ Server settings page.

  • A variable binding for the alert data specified in the snmp_trap.gsp alert notification template - the alert definition name and the "short reason" for firing. Note that Alert templates may be customized, as described in Tailor Alert Notification Templates.

Including more variable bindings in SNMP messages

For richer capability, you can configure a SNMP notification as a step in an escalation. An SNMP notification in an escalation can be configured with additional variable bindings. For more information, see Configure and Manage Escalations

To configure an SNMP notification action enter:

  • IP Address - the address and port of the target NMS.

  • OID - The OID of the notification to send, which will contain the alert details specified in the snmp_trap.gsp, template.

  • Notification Mechanism - The type of SNMP notification to send:

    • v1 Trap

    • v2c Trap

    • Inform