Chat now with support
Chat with Support

Foglight for Integrations 5.9.4 - User and Reference Guide

Using Foglight for Integrations Reference

Selecting a Configuration Item in a Service Builder

The third-party Configuration Items can be used in building services. This can be done by selecting All Models and then opening the CI Model. This shows all Configuration Items fed from third-parties. These can be selected and included in the service. For example, accounts payable may want to include Configuration Items in a service because it is possible Foglight is not monitoring them, but rather by a third-party system.

Forwarding Alarms to Third-Party Systems

You can forward any alarm into another third-party system. A new action, called IntegrationAction, has been introduced to allow the user to forward these alarms.

Forwarding Alarms

1
On the navigation panel, under Dashboards, click Administration > Rules & Notifications > Create Rule.
2
Click the Rule Definition tab, and in the Rule Name box, type a name.
3
Click to select the Simple Rule option button and the Event Driven option button, then select AlarmSystemEvent from the Event Name drop down.
4
Set the Rule Scope to No Scoping Query.
5
Click the Rule Variables tab to add the rule variables alarm_event and script and set the following:
a
In the Type field, click to select the Expression radio box to add the alarm_event variable.
b
In the Name box, type alarm_event and in the Expression/Message box type @event.
c
d
In the Type field, click to select the Message radio box to add the script variable.
e
In the Name box, type script and in the Expression/Message box type the path of the script you want to use. For example, /tmp/XMLDump.sh.
TIP: On the navigation panel, under Dashboards, click Administration > Cartridges > Components for Download, and then click Integration Samples. Save or Open the file and locate the script called sample_alarm_parser.pl. This script is an XML parser that parses the outgoing XML data. It can be used as a template to start building your own script.
f
6
Click the Conditions and Actions tab and click the Fire heading.
a
In the Condition box, type true and then click the Validate Condition icon .
b
Click the Action tab, and set Action Type to Entering.
c
In the Action list, click IntegrationAction.
d
e
For alarm system event, click Default and select alarm_event from the Rule/System Variables.
f
Click Change.
g
For COMMAND_LINE, click the Default link, select script from the Rule/System Variables and click Change.
7
Click Finish to save the rule.
2
In the Action Parameter Editor, click the User-Defined tab and type false to no longer trigger the action when that update occurs.
3
Click the Change button to save the changes.
4
To set to true, click Default.

For more information about rules, see the Foglight Administration and Configuration Guide.

Creating an XMLDump Script

This script takes Foglight Alarm XML data and dumps it into the /tmp directory. This would be replaced with a script used to transform the XML data into the format that the receiving third-party system requires.

2

The XML data generated contains information about the alarms as they exist in Foglight.

For Foglight generated alarms, the ruleId, ruleName, and sourceName are added to the XML data.
For all alarms, the uniqueId, createdTime, clearedTime, and acknowledgedTime element data are provided in the XML data output.
The type element data on outgoing Configuration Items is set to the Foglight topology type for Foglight generated alarms.
For Third-party alarms, the type is from the type property that is passed in on the Configuration Item.
Related Documents