Chat now with support
Chat with Support

Foglight for Integrations 5.9.8 - User Guide

Using Foglight for Integrations Reference

Forwarding Alarms Samples

Quest supports XML data generated by the Integration action when used in forwarding alarms to other third-party or home grown solutions. Quest does not support derivative works created from the provided samples that use the generated XML data to feed into third-party systems.

Figure 4. Forwarding Alarms to Third-Party Systems

The following forwarding samples are available:

•
Quest Management Xtensions (QMX)
•
CA Unicenter
•
HP OVO
•
IBM Tivoli TEC
•
SCOM (see the CartridgeForIntegration_SCOMsamplesetup.pdf for setup instructions)

Obtaining Integration Samples

To obtain an integration sample:
1
On the navigation panel, under Dashboards, click Administration > Cartridges > Component for Download.
The Components for Download page appears.
2
Under the Name column, click Integration Samples.
The File Download dialog box appears.
3
Click Open to view the integration samples.
Optional — Click Save to copy the zip file to another location.
4
Unzip the file to view the integration samples and begin working with them.
Each of the Integration Samples sub-directories contains a Setup.pdf that contains instructions for establishing that particular feed.
* 
NOTE: Each of the Integration Samples sub-directories contains a Setup.pdf that contains instructions for establishing that particular feed.

Receiving Third-Party Alarms in Foglight

Quest supports receiving well-formed and valid XML data into Foglight for Integrations.

Related topics:
•
Preparing the Data
•
Viewing Third-Party Alarms
•
Working with Configuration Items

Preparing the Data

XML data is used to receive alarms from third-party systems into Foglight. Transformers are provided with the Foglight for Integrations to handle the data appropriately.

XML Elements
Table 1. XML elements and descriptions
XML Element
Description
<configurationItem>

This element identifies that a Configuration Item is being passed in the XML. Attributes can also be attached with the element. They are:

updateMode:

“none/merge/replace”

•
None — no CI changes
•
Merge — non-existing properties added, single properties are replaced, and list properties have content merged
•
Replace — CI contents replaced by data in the XML. This is the default if updateMode is not specified.

updateRelationships:

Normally when a Configuration Item is written, it removes all properties and relationships (like the Parent and Child). However, an alarm may come in with Configuration Item updates but without all the relationship information. This setting allows you to update the Configuration Item without affecting any previously defined relationships.

<type>

This required element signifies the type of Configuration Item.

<sourceId>

This required element should be the unique and persistent ID of the Configuration Item to that technology monitor.

<name>

This required element is the name of the object being passed.

<status>

This required element is the status of the Configuration Item as it relates to the sending Technology Monitor. Valid values are Active and Inactive.

<property>

This optional element is used to pass additional properties about the Configuration Item.

<propertyName>

A valid property as defined in Configuration Item properties administration.

<propertyValue>

A supplied value for the Configuration Item property.

<technicalLevelAgreement>

This optional element identifies that a Technical Level Agreement is being passed in the XML.

<sourceId>

This required element should be the unique ID of the Technical Level Agreement to the technology monitor.

<name>

This required element is the name of the object being passed.

<status>

The required element is the status of the Technical Level Agreement as it relates to the sending Technology Monitor. Valid values are Active and Inactive.

<property>

This optional element is used to pass additional properties about the Technical Level Agreement.

<propertyName>

This element indicates a valid property as defined in Technical Level Agreement properties administration.

<propertyValue>

This element indicates a supplied value for the Technical Level Agreement property.

<alarm>

This element identifies that an alarm is being passed in the XML. Parameters can also be attached.

When the severity of an alarm changes, the previous alarm is closed and a new alarm is opened.

<sourceId>

This required element should be the unique id of the alarm to that technology monitor.

<severity>

The required element is the severity of the alarm. Valid severity values are: 0-Normal, 2-Warning, 3-Critical, 4-Fatal. Any severities sent in with any other values are mapped to 4 and are displayed in the alarm browser.

<startTime>

The required element is the start time of the alarm.

<endTime>

This optional element is the end time of the alarm.

<message>

This required element describes the alarm that is occurring.

<property>

This optional element is used to pass additional properties about the object.

<propertyName>

A valid property as defined in Alarm properties administration.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating