Foglight for Integrations 5.9.4 - User and Reference Guide

Configuring ServiceNow Integration

Foglight ServiceNow Integration allows using ServiceNow API to create ServiceNow incidents for Foglight alarms.


	NOTE: ServiceNow Integration does not apply Foglight Service Alarm Filters when syncing alarms to ServiceNow.

Requirements

Using Foglight ServiceNow Integration requires a ServiceNow account with ServiceNow roles:

•

incident_manager

•

personalize_choices

Configuring ServiceNow integration

Connect to ServiceNow instance:

Select Dashboard Administration > Integration > ServiceNow Integration to open ServiceNow configuration dashboard.

Click “Get Started” to start the configuration wizard.

In the first wizard screen, ServiceNow Instance Account, connect to the ServiceNow instance by providing the ServiceNow URL and credential

Click “Next” and Foglight will verify the provided ServiceNow instance URL and credential, if the verification passes, it will display the “Summary” page.

Then click “Finish” and Foglight will display the ServiceNow Integration main Dashboard, including “General Setting” tab and “Service Synchronization” tab.

“General Setting” tab displays current ServiceNow Integration settings and status.

“Service Synchronization” tab lists all Foglight services and allows user to configure service based alarm to incident synchronization.

Configuring service based synchronization

Foglight ServiceNow supports service based alarm synchronization, users can configure service based alarm synchronization in “Service Synchronization” dashboard:

To configure service synchronization:

Find the Foglight service or child service you want to operate in service table

Click the “Category” column for the selected service, and select the ServiceNow Category of the alarms you want to synchronize to.

Click “Assigned Person” OR “Assigned Group” to select the default assignee for all synchronized ServiceNow incidents.

Click “Enable/Disable Synchronization” to enable synchronization for the selected service.

Click the “Save” button to save all changes, this step is required because the configuration only works after it is saved.

If you want to keep some irrelevant alarms from falsely causing a service outage, define an alarm filter in the Service Builder. To define an alarm filter:

Select Dashboard Services > Service Builder.

Click the Alarm Filters to open the Alarm Filters dialog box.

Figure 7. Open Alarm Filters dialog box

Click Add in the Alarm Filters dialog box. The Add Alarm Filter dialog box appears.

Figure 8. Add Alarm Filter dialog box

Then, select one or more filter options:

Figure 9. Select filter options

•

By Rule—select the By Rule check box and choose a rule for which its alarms are to be included or excluded. You can define more than one alarm filter for the same rule.

•

Alarms—select the types of alarms to include or exclude.


	NOTE: If both Include and Exclude filters are defined, Foglight includes alarms that are specified in the Include filters as long as they are not excluded by the Exclude filters. If only Include filters are defined, all alarms are excluded except those specified in the Include filters.If only Exclude filters are defined, all alarms are included except those specified in the Exclude filters.

•

Groovy Script—refine the filtering by running an optional groovy script. The current alarm is the only parameter passed to this script, meaning you can filter on anything that is referenced by the alarm. An example of a groovy script is:

@alarm.get('topologyObject').getType().getName() ==
'Windows_System_System_Table'

Click Create.

The filter is saved on the Alarm Filters list and the number is displayed to represent the number of filters created for the selected component.

After applying the Alarm Filters, irrelevant alarms will not be synchronized to ServiceNow.