AlertOps and Devo

AlertOps’ alert management system can be integrated with Devo to receive and respond to all (predefined status mappings) alerts through email, SMS, push notification or phone alerts. AlertOps would ensure that the alert/job status would reach the appropriate team by using proper workflows, escalation policies and schedules. Based on your ruleset, incidents can be automatically opened and closed, depending on what kind of alert Devo reports.

The above scenario and scope for integration is due to the fact that AlertOps has a very flexible and simple API/Webhook configuration feature that can be leveraged with Devo's alert and notification capabilities.

AlertOps - Inbound Integration

We can define rulesets in AlertOps so that Devo can send out alerts to the AlertOps platform. AlertOps would ensure based on these notifications received, that it would always reach out and assign to the correct person/team by utilizing its escalation policies, schedules, and workflow features.

AlertOps provides Inbound Integrations to integrate with numerous monitoring, chat and ITSM tools. You can configure an inbound integration for Devo.

At a high level this is how the flow looks like, you define an API integration in the AlertOps platform by defining settings like Integration Name, Escalation rules, recipient users/groups. Once an integration is defined, a unique API URL is generated. This acts as webhook or the gateway through which notifications from Devo reach AlertOps and thus an incident/alert is created correspondingly. The API can be defined with various settings like URL mappings, filters, escalations etc. as required. Devo has to be defined with a HTTP-JSON delivery method for an alert

To configure an Inbound Integration in AlertOps to receive alerts from Devo,

  • Under 'Integrations' select 'Inbound Integrations', select the category 'API' and then select add 'Add API Integration'

  • There are numerous integration options available in AlertOps, select Devo (else select Custom)

  • Once you selected the integration, you can then specify basic settings like the integration name, escalation policy, names of the recipients/groups for which the alerts must be assigned to.

  • Once you click save, the API Integration will be created, and you will be given a unique URL which acts as the access point and needs to be configured at the source (in this case Devo), to send alerts. You can find the integration you just created, and you can give advanced settings and define various configurations for the alerts to be received and processed. For example, you can define when to open and close alerts based on the payload obtained from the API call, filters etc.

  • Make a note of the API URL, which will be used in Devo, so it calls a HTTP POST request to this URL with the body in JSON format containing the alert specific information. AlertOps automatically creates an alert when the status variable (status) contains '0/700' (denotes started/unread). The incident will also be closed automatically when the status '300/600' (denotes closed/recovery) is received from Devo.

  • You can similarly define URL mappings as you want, owing to the flexibility provided by AlertOps’ OpenAPI/Plug-and-Play integrations. You can provide other filters and match with regex expressions as well. You can also test the generated URL with the sample data provided.

Configuration of Devo for the Integration,

  • To manage delivery methods for an alert, in your Devo portal go to 'Administration' > 'Alert Configurations' > and then 'Delivery Methods' in the top tab

  • Make sure you have the adequate permissions to setup delivery rules.

  • Click the New button at the top right (if there are no methods created yet, this button appears in the center). Select HTTP-JSON.

  • Give the method a name, for URL paste the AlertOps Inbound Integration API URL. Language is English and Content-Type is application/JSON. You can leave the rest of the sections default. Apply

  • Now jump to your AlertOps environment. Under Integrations in the left menu, select Inbound Log. You should have received a message from Devo. Select the Message ID. The Mapping Status may be Mapped Ignored - Status Mismatch. This is fine.

  • The Body of the message will contain the Activation Code. You can search for this in the body. Copy the activation code

  • Now in your Devo environment, click the 'Pending Activation' under the status of your newly created delivery method. Paste the Activation Code. Apply.

Thats it! You have configured a HTTP-JSON delivery rule for an alert configuration. Any alert will be sent to AlertOps for incident management.

Message logs, alert specific information can be viewed in the “Inbound Log” section in AlertOps Dashboard. Alerts can be viewed in the ‘Alerts’ tab as well.

Alert Triggering Information:

AlertOps will automatically create an incident when a new alert is received from Devo when the status contains "0/700".

If an alert with status "0/700" matches an existing Open Alert, AlertOps will recognize the new alert as a duplicate and ignore the alert.

The alert will be recorded in the Inbound Messages table as “Mapped Appended.”

AlertOps will automatically close the same incident when an alert with status contains "300/600".

References

AlertOps Integration Guides

General Restful API Guide

Devo Reference

Devo Alert Monitoring Tables - For statuses/priorities mapping

Did this answer your question?