This integration allows collecting alarms from Foglight to create events in OBM through OA. The template name is Foglight Alarm to OBM Event (OA).
This action sends HTTP requests at a scheduled interval to collect new alarms from Foglight to create events in OBM.
This action sends HTTP requests at a scheduled interval to detect cleared alarms from Foglight to send normal events to OBM to close the corresponding events.
Below is the default data mapping for this integration template.
|Source Entity||Target Entity Attribute||Target Entity Attribute Details|
(a static value that the integration sends for the "Category" attribute of the OBM event)
(the "ID" of the Foglight alarm)
(a combination from the "ID" and the "Severity" of the Foghtlight alarm)
(the "Message" of the Foglight alarm)
(the "Name" of the Topology Object of the Foglight alarm)
(a combination from the "Name" of the Foglight Topology Object of the Foghtlight alarm)
The ZigiOps checks the available values in the following order:
(the hostname of the ZigiOps server)
(a static value that the ZigiOps sends for the "Subcategory" field of the OBM event)
(the time when the Foglight violation has been opened)
(a combination of the "Rule Name" and the "Name" of the Topology Object of the Foglight alarm)
This section provides information about the recommended considerations, which you should consider before enabling the integration.
OBM handles the correlation based on the "Correlation Key" and "Close Key" attributes that the integration supplies with each event.
The predefined templates comply with the specifics of the integrated systems. It is recommended to confirm if your integrated systems have any required fields, which must be reported so that you can map them accordingly. Note that if a required field is not mapped, the action might fail. In this case, you could review the troubleshooting page for more information about the action's execution history.