Skip to main content

ServiceNow Management: Maintenance Window Filters

As of Add-ons release v2.5, you can alter the behavior of maintenance window filters created from ServiceNow change tickets. The default maintenance window behavior can be changed when the ENABLE CHANGE INTEGRATION FOR MAINTENANCE WINDOW MANAGER option is selected.

For configuration information, see ServiceNow Management Integration Configuration.

Default Behavior

By default, the affected CIs listed in the ServiceNow change are mapped to the Moogsoft Onprem source field.

For example, given the following affected CIs:

  • Node 1

  • Node 2

The maintenance window filter would be constructed as:

source IN ["Node 1", "Node 2"]

Filter Examples

You can modify the constructed maintenance windows by changing the fields listed in the AFFECTED CI FIELDS and IMPACTED CI FIELDS properties, and by togging the JOIN USING ‘AND' property.

At least one affected CI still needs to be present in the change record for the maintenance window to be triggered, but both affected and impacted CIs can be combined in the maintenance window filter, as illustrated in the following simplified examples.

Example 1. Default behavior

The following settings produce the default behavior:

Setting Name

Setting Value

AFFECTED CI FIELDS

source

IMPACTED CI FIELDS

JOIN USING ‘AND’

false



Example 2. source matches either affected CI or impacted CI

The following settings:

Setting Name

Setting Value

AFFECTED CI FIELDS

source

IMPACTED CI FIELDS

source

JOIN USING ‘AND’

false

Given this input:

Affected CIs

Node 1, Node 2

Impacted CIs

Node 3

Produce this maintenance filter:

source IN ["Node 1", "Node 2", "Node 3"]


Example 3. source matches affected CI OR custom_info.service matches impacted CI

The following settings:

Setting Name

Setting Value

AFFECTED CI FIELDS

source

IMPACTED CI FIELDS

custom_info.service

JOIN USING ‘AND’

false

Given this input:

Affected CIs

Node 1, Node 2

Impacted CIs

E-Commerce

Produce this maintenance filter:

source IN ["Node 1", "Node 2"] OR custom_info.service IN ["E-Commerce"]


Example 4. source matches affected CI AND custom_info.service matches impacted CI

The following settings:

Setting Name

Setting Value

AFFECTED CI FIELDS

source

IMPACTED CI FIELDS

custom_info.service

JOIN USING ‘AND’

true

Given this input:

Affected CIs

Node 1, Node 2

Impacted CIs

E-Commerce

Produce this maintenance filter:

source IN ["Node 1", "Node 2"] AND custom_info.service IN ["E-Commerce"]


In this section: