The following sections cover useful alarm operations for Experience Manager test alarms and describe how these vary from other integrations:
When you acknowledge a test alarm, the alarm severity changes to OK and remains at OK regardless of the state of occurrences for the alarm. If the alarm is not acknowledged, the test alarm changes from OK to the current state.
Use the reset operation when you need to reset alarm counts and averages. For example, when introducing a new version of a Web server and the alarm history no longer applies.
To reset an alarm’s response time values and occurrences, from the Alarms view, right-click an alarm, then click Reset.
Response time and occurrence values are set to 0.
To rerun a test from an alarm, from the Alarms view, right-click a synthetic test alarm, then click Run Test.
The test associated with the alarm is run.
Experience Manager leverages Managed Object Definition Language (MODL) to generate elements for a received alarm. MODL consists of a DTD (Data Type Definition) that follows rules for structuring an XML document.
To automatically remove test elements after closing or deleting all their associated alarms:
Open the database/examples /bemHierarchy.xml file in any text editor.
Change hold=yes to hold=no for the furthest leaf nodes.
Move the modified bemHierarchy.xml file to the database directory so that Operations Center does not overwrite the changes.