Hyperic HQ 4.x Documentation : ui-Alert.New
This page last changed on Jul 14, 2009 by mmcgarry.
Topics marked with * relate to HQ Enterprise-only features. The New Alert Definition page allows you to define the properties and condition set for an alert definition. After you define the alert properties and condition set, and save your changes, you can define actions for HQ to perform when an alert is fired. Navigate to the New Alert Definition PageTo access the New Alert Definition page,
Define Alert Properties
Define Alert Condition SetThe options for defining alert conditions and firing rules vary by the type of resource to which the alert applies, and your version of HQ. Condition SetAn 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 HQ version. If a condition type is not supported by your version of HQ 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.
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).
Define Additional Conditions*In HQ Enterprise, 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*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 Recovery Alerts. Enable ActionsYou can make the condition absolute - (one strike you're out) or fire after the condition occurs repeatedly. Choose either:
Option removed in 4.1 In versions of HQ Enterprise previous to 4.1, you could configure an alert definition to fire when its conditions have meet met continuously for a specified portion of an period of time. The option - "When conditions are exceeded for x within a time period of y minutes" - was removed in HQ 4.1. Enable Action FiltersAn action filter can be used to control alert firing and alert actions. Disable an Alert Definition upon FiringClick 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 HQ 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. For more information, see Recovery Alerts. Disregard Control Actions for Related Alerts.The Disregard control actions that are defined for related alerts option appears on New Alert Definition pages for resources that support control actions. This option only applies when:
Under these circumstances, this configuration option ensures that if multiple alerts are fired within a short period for resources that are members of the same application, only one control action will be executed. For example, this would prevent a server from being restarted several times in a short period of time for the same alert conditions. For instance, you might have an alert with an action to restart a Tomcat server if the JVM Free Memory got too low and another alert with an action to restart the same server if the JVM Active Thread count got too high. If both alerts fired at the same time and they were filtering control actions, only 1 restart control action would be executed and not two. Option removed in 4.2 Versions of HQ previous to 4.2 also had a Filter notification actions that are defined for related alerts option to prevent multiple notification when alerts fire for resources on the same platform. In HQ 4.2, the option was removed. HQ 4.2 provides enhanced functionality for global control of notification volume. For more information, see Set a Notification Throttle. Save the Alert DefinitionAfter defining alert properties and conditions, click OK to save the alert definition. The alert definition is created, and complete if you do not want to configure any alert actions. The Alert Definition page appears. This page allows you to edit the alert properties and conditions, and add alert actions, as desired. Define Alert ActionsYou can use the tabs at the bottom of the Alert Definition page to set up one or more actions to be performed when the alert fires. See the "Create or Edit Alert Actions" section on the associated help page for instructions. Note: Defining actions for an alert definition is optional. Related Information |
![]() |
Document generated by Confluence on Apr 20, 2010 15:01 |