AlertOps and Zebrium

AlertOps’ alert management system can be integrated with Zebrium 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 incident Zebrium 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 Zebrium's alert and notification capabilities.

AlertOps - Inbound Integration

We can define rulesets in AlertOps so that Zebrium can send out incidents 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 Zebrium.

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 Zebrium 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. Zebrium has to configured with an outbound webhook integration.

Configure Inbound Integration in AlertOps

1. Navigate to Configuration àIntegrations àAdd API Integration à API Integration Detail page.
2. Select Zebrium
3. 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.
4. 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 Zebrium), 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.
5. Make a note of the API URL, which will be used in Zebrium, 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 (incident_state) contains 'open'. The incident will also be closed automatically when the status 'muted' is received from Zebrium.
6. In Advanced Settings you can define URL mappings as you want in the Rules for Opening and Closing Alerts. You can provide other filters and match with regex expressions as well. You can also test the generated URL with the sample data provided. 

Configure Integration in Zebrium 

1. In your Zebrium portal, select the Menu icon in the top right corner and then select 'Outbound Integrations'
2. Select 'Create Outbound Integration' and for type select 'Webhook'
3. Give the webhook a name, select 'Yes' for 'Send to this channel on first occurrence'
4. For Service Groups - select Any.
5. In the fully-qualified URL text field, paste the AlertOps Inbound Integration API URL.
6. Select None for Authentication. Create.

Thats it! You have configured an outbound webhook integration for incidents in Zebrium. Any incident 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 Zebrium when the incident_type contains "open".

If an alert with status "open" 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 incident_state contains "muted".

References

AlertOps Integration Guides

General Restful API Guide

Zebrium Docs - 'Search 'Webhooks' for more payload information'