Chat now with support
Chat with Support

Foglight for Integrations 7.3.0 - User 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.

To select all Configuration Items fed from third-party systems:
1
In the Service Builder, create a service.
For more information about how to create a service, see the Foglight User Guide.
2
On the Service Builder view, click All Models.
3
Select the Configuration Items you want to add to the service.
4
Click Add.
All Configuration Items fed from third-party systems appear in the view. These can be selected and included in the service.
Properties of CI Model:
Value — The value of the property.
Data Type — The data type is a data-object template, and it determines the structure of a data object. Examples of data types are Host, AppServer, WebLogic, WebSphere, Agent, and Event.

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.

* 
NOTE: For Microsoft System Center Operations Manager (SCOM) integration rule setup, see the CartridgeForIntegration_SCOMsamplesetup.pdf. For all other integration samples, see Forwarding Alarms .
* 
NOTE: A sample Alarm Integration rule is provided when Foglight for Integrations is installed. It is disabled by default. Once enabled, it can be modified to the specific requirements needed to forward alarms to a third-party system.

Forwarding Alarms

* 
NOTE: This section pertains to all integration samples except the Microsoft System Center Operations Manager (SCOM) integration sample. For the SCOM sample, see the CartridgeForIntegration_SCOMsamplesetup.pdf.
To forward an alarm to a third-party system:
1
On the navigation panel, under Dashboards, click Administration > Rules & Notifications > Create Rule.
The Create Rule view appears.
2
Click the Rule Definition tab, and in the Rule Name dashboard, 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 Severity Level 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.
The event object is passed to the output script.
c
Click <<Add.
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.
This script is replaced with the script being used to feed the third-party system.
* 
NOTE: On the Windows platform, if running a Perl script, the Expression/Message must begin with “perl” followed by the full path of the script being run. For example: perl c:\dell...\script_name.pl
 
* 
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
Click <<Add.
6
Click the Condition tab and click the Fire heading.
a
In the Condition box, type true and then click the Test Rule Logic button.
b
Click the Email Notification & Recovery Actions tab, and set Action Type to Entering.
Entering is the default value.
c
In the Action list, click IntegrationAction.
d
Click <<Add.
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.
Four action parameters listed in the preceding image.
•
Include Alarms being Acknowledged
•
Include Alarms being Cleared
•
Include Alarms being Opened
•
Include User Defined Data Updates
These are used to control what alarm updates trigger this action. The value can be either true or false.
When these are set to true, and when they occur, they trigger the integration action.
7
Click Finish to save the rule.
To change the value to false:
1
Click on the default link next to each to change.
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.
5
Click Go To Action List go back to Rule Editor, click Next and then click Save to save the rule.
For more information about rules, see the Foglight Administration and Configuration Guide.

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.

To create an XML Dump script:
1
Create a script and type the following:
#!/bin/sh
cat > /tmp/dumpit.out.$$
echo "made it out!"
2
Save this script to the /temp directory.
XML Information

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.
•
All properties of the alarm or topology objects are passed on the outgoing feed. If the property is another object, only the name of the object (for example, severity) is used.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating