URL Mapping

The URL Mapping section contains the control configuration for the alerts. There is quite a bit of flexibility. This example uses the JSON body in the sample data box.

At a minimum, you must configure the Source, Source Name, Status Field, and Status Control actions (Open, Close, and Update Alert).

Mapping AlertOps will match each incoming alert to previous alerts using the following: Source + Source Name.

Optionally, AlertOps will include the Source ID (if provided) in the alert matching algorithm.

Source is a static field which is used both for mapping and grouping. You can also use Source for reporting purposes.

Source Name can either be a static, or fixed value, or it can be a dynamic value using data from the inbound alert.

  • For Static values, check the Static box and a static value needs to be provided in the Source Name field.
  • For Dynamic values, the inbound JSON/Form field needs to be provided in the Source Name field. Static checkbox needs to be unchecked and the value must be left blank for matching with any inbound field value. If it is not left blank, the value is then used to match with inbound data.

The Status field will be used to determine what action should be taken: whether to open a new alert or close an existing alert that is not closed.

Along with the Status field, the Alert action fields tell AlertOps which action should be taken.

The API URL is the endpoint for the integration, use this to configure the web hook endpoint in your source system.

Sample Data can be used to store a sample JSON body for reference. You can also use the Sample Data to test your configuration.

Nested Objects

If you are mapping a field that is composed of nested object data, such as in the following example:

“issue” : {“id”: “31999”, “key”: “ABC31999”}

You can map the id field using the following syntax:

issue^id

likewise, you can map the key as follows:

issue^key.

Arrays

If you are mapping an field that has arrays, such as in the following example:

{"evalMatches":[{"value":183910,"metric":"rabbit_mq_disk_space_free_total","tags":null}],"message":"Disk Space for server in UAT is above below 19GB testing","ruleId":12,"ruleName":"Server Disk space full in UAT","ruleUrl":"http://localhost:3000/dashboard/db/axon-blackbox-uat-infra-metrics?fullscreen\u0026edit\u0026tab=alert\u0026panelId=8","state":"alerting","title":"[Alerting] Server Disk space full in UAT"}  

You can map the metric field using the following syntax: evalMatches_0^metric 

evalMatches_0^metric returns rabbit_mq_disk_space_free_total

Sample Data and API URL

The API URL is the endpoint for the integration, use this to configure the web hook endpoint in your source system.

Sample Data can be used to store a sample JSON body for reference. You can also use the Sample Data to test your configuration.

The Sample Data box allows you to store a sample of the JSON data used in this integration. Use this both as a reference and also for testing purposes. You can test your configuration using the Test URL button along with the sample data.

Refer to the Web API Testing and Troubleshooting section for details on how to test the Web API Integration.

Short Text and Long Text Fields

The Short Text and long text fields are not required, but it is recommended that you configure each of these.

The Short Text field allows you to set the field which maps to the AlertOps Short Message property.

*The Short Text / Short Message is the message used in SMS and voice notifications.

*You can also customize the Short Message using a combination of static and dynamic text. Refer to the Advanced Options link below.

If there is no Short Text field configured, AlertOps will use the Long Text field in its place. If there is no long text, AlertOps will use the entire JSON body as the Short Message text.

The Long Text field allows you to set the field which maps to the AlertOps Long message property.

*The Long Text / Long Message is the message used in Email and Push notifications.

*You can also customize the Long Message using a combination of static and dynamic text. Refer to the Advanced Options link below.

If there is no long text, AlertOps will use the entire JSON body as the Short Message text.

The API URL is the endpoint for the integration, use this to configure the web hook endpoint in your source system.

Sample Data can be used to store a sample JSON body for reference. You can also use the Sample Data to test your configuration.

Source Name field – Static vs. Dynamic

AlertOps will match each incoming alert to previous alerts using the following:

Source + Source Name.

The Status field will be used to determine what action should be taken, whether to open a new alert or close and existing alert that is not closed.

The Source Name field can either be static, or fixed, or it can be dynamic.

With a dynamic Source Name field you can set up multiple integrations using a single end point. Each of these integrations can then use different processing rules, such as assignment to different groups, or different escalations using Message Rules.

Example 1 – Static Source Name

The Source is ‘AlertMon’ and the Source Name is static ‘System’.

AlertOps next looks at the Status to determine what actions should be taken.

Status is OPEN, PROBLEM or FAIL

There are no alerts in the system with a matching combination of Source plus Source Name.

A new alert is opened.

Example 2 – Static Source Name

The Source is ‘AlertMon’ and the Source Name is static ‘System’.

AlertOps next looks at the Status to determine what actions should be taken.

Status is CLOSED, CLEARED, OK or PASS

There is an alert in the system with a matching combination of Source plus Source Name.

A alert in the system is CLOSED.

Example 3 – Static Source Name

The Source is ‘AlertMon’ and the Source Name is static ‘System’.

AlertOps next looks at the Status to determine what actions should be taken.

Status is UPDATE

There is an alert in the system with a matching combination of Source plus Source Name.

A new message is added to the alert message thread.

Example 4 – Dynamic Source Name

The Source is ‘AlertMon’ and the Source Name field contains ‘Service1’.

AlertOps next looks at the Status to determine what actions should be taken.

Status is OPEN, PROBLEM or FAIL

There are no alerts in the system with a matching combination of Source plus Source Name.

A new alert is opened.

Example 5 – Dynamic Source Name

The Source is ‘AlertMon’ and the Source Name field contains ‘Service1’.

AlertOps next looks at the Status to determine what actions should be taken.

Status is CLOSED, CLEARED, OK or PASS

There is an alert in the system with a matching combination of Source plus Source Name.

A alert in the system is CLOSED.

Example 6 – Dynamic Source Name

The Source is ‘AlertMon’ and the Source Name field contains ‘Service1’.

AlertOps next looks at the Status to determine what actions should be taken.

Status is UPDATE

There is an alert in the system with a matching combination of Source plus Source Name.

A new message is added to the alert message thread.

Source Name Static vs. Dynamic

You can use Static or Dynamic mapping for the Source Name.

Static mapping is a simplified means when you want all incoming alerts to share the same Message Rules or Recipients.

Dynamic mapping, however, allows you to route alerts using different Message Rules for escalation purposes, and also route to different recipients.

With a Dynamic Source Name, you create multiple Integrations using a different value for the Source Name, and then set your integration rules accordingly. Each of these Integrations will share the same endpoint.

  • For Static values, check the Static box and enter the same value in both fields.
  • For dynamic values, uncheck the static box, enter the field name in the first box and then enter a matching value in the second box.

Method Setting Options

Method settings include POST or GET.

Content Setting Options

Content settings include:

JSON

FORM URL encoded(GET)

FORM data

Did this answer your question?