Foglight for Integrations 6.3.0 - User Guide

Clearing Alarms

Alarms from third-party systems may provide start and end times for their alarms. These start and end times fed into Foglight are stored in the user-defined properties of the alarm. By default, any alarm being processed with an end time in the user-defined properties, are not cleared (this occurs when the Auto_Clear_Integration_Alarms_with_EndTime registry variable is set to false).

In certain instances, a third party may send an alarm with an end time in the future. This occurs when the technology monitor is unable to provide an indication that an alarm condition is no longer occurring. However, the third-party systems check again and send another alarm if the condition is still occurring. For example, a condition is checked every 15 minutes. If at 12:00 A.M. the condition is true, an alarm is sent with a start time of 12:00 A.M. and an end time of 12:15 A.M.. The end time is 12:15 A.M. because the condition is checked again at that time and if still true, another alarm is sent.

In Foglight, we may not want to automatically clear the alarm because the user would never see the alarm in the browser and know that it is occurring. We also do not want the user to have to manually clear all these alarms.

To automate the clearing of future dated alarms, the registry variable, Auto_Clear_Integration_Alarms_with_EndTime, can be changed. The default value is false. When true, the alarm with a user-defined end time is cleared automatically when the alarm is first received. When set to false, any alarm with a user-defined end time is not cleared in that manner. Otherwise, these must cleared using the user interface or by using the new Clear Integration Alarm Rule. This new rule is disabled by default. When enabled, this rule runs every five minutes. This rule looks for third-party alarms with an end time in the past that have not been cleared, and then clears the alarm. This keeps the alarm in the browser until the end time is reached.

NOTE: If the registry variable is set to true, the Clear Integration Alarm Rule does not not close any alarms because the alarm processing would have already closed any alarm with an end time.

Processing Alarms

The processing of third-party alarms manages the updates made to the user-defined properties.

Working with Configuration Items

Any monitored object coming from an external source is considered a configuration item. A Configuration Item is anything that can be monitored. For example, a host, a database, a memory component, or a CPU. The hierarchy is not pre-defined. If an event consolidator sends an event tracking an interface on a switch, a Configuration Item is created for that interface. If the Event Consolidator sends information about the switch and the relationship between the switch and the interface, then two Configuration Items are created: one for the switch and one for the interface. In addition, the “detail” property (which is inherited in the model) of the switch is set to the interface, allowing Foglight to understand that some Configuration Items are “parents” to other Configuration Items.

Each Configuration Item is unique. It has a combination of technology monitor and sourceId. The number of Configuration Items that are created depends on the types of systems sending alarms into Foglight. If two different technology monitors manage the same Configuration Item (a server for example), two different Configuration Items are created. If a technology monitor manages a Configuration Item which is the same as a device Foglight manages (and appears in the Host model), it creates a unique Configuration Item.

Foglight for Integrations provides the Foglight Administrator the capability of defining CI Properties using the CI Property view. In this view, the Administrator can define a new property along with Type and Is List options.

NOTE: In a federated environment, it is important to keep CI Properties consistent between federated Management Servers. For example, if one federated Management Server has a property called External asset id that is a type of Integer and Is List, other federated servers should have a property called External asset id that is a type of Integer and Is List. CI Properties must be consistent across federated servers.

Reviewing the Property Details of a Configuration Item

For details on the state of the Configuration Item, click the down arrow on the Additional Details view.