Chat now with support
Chat with Support

Foglight for Integrations 5.9.8 - User Guide

Using Foglight for Integrations Reference

Viewing Third-Party Alarms

Alarms in Foglight indicate significant changes in the state of a monitored resource. An alarm can be generated for a problem, for a resolution of a problem, or the completion of a task. Alarms contain a message that may include details of the data that caused the rule to fire.

Figure 5. Alarm pop-up
Click the History tab.
Acknowledge — if acknowledged, it indicates that the alarm has been examined. The user name of the person who acknowledged the alarm appears in the Ack’ed By column for that alarm.
Acknowledge Until Normal — this acknowledges the current alarm and all consecutive alarms that the rule fires on the same instance. This option is available to an outstanding (not yet cleared) alarm only.
For example, assume that an alarm goes from Warning to Critical to Warning to Fatal to Critical to Clear. The Foglight operator might recognize the alarm at the Warning stage as “a problem related to the batch job”. If so, the operator might acknowledge the warning, and all subsequent alarms until Normal, so anyone else looking at the alarm console knows that they have looked at the problem.
Clear — clears the alarm from the list.
Cancel — returns to the previous view.

Filtering Alarms

You can filter the list in the outstanding alarms view using one or more of the following criteria:

Hiding Columns in the Alarms View

You can hide any of the columns in the Outstanding Alarms view.

Acknowledging Alarms

The Ack.ed By column in the Outstanding Alarms view indicates whether an alarm has been acknowledged. If an alarm has not been acknowledged, the column is blank. If an alarm has been acknowledged, the column displays the user name of the person who acknowledged it. This information is also stored in an audit report.

Click Acknowledge.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating