Webhook Connection for Opsgenie

Webhook connections rely on HTTP endpoints that tell Sumo Logic where to send data. You can set up any number of connections. 

Sumo Logic to Opsgenie Integration

Sumo Logic alerts can send webhook alerts to Opsgenie that acts as a dispatcher and determines the right people to notify based on your on-call schedule.

To add a Sumo Logic integration in Opsgenie, do the following:

1. Go to Opsgenie Integration Page.
2. Specify the following parameters:
   • Provide the Name.
   • Add the team who will be notified of Sumo Logic Alerts.
   • Copy the Integration Url, it is used in Sumo Logic while setting up the Webhook Connection.
   note

   For Free and Essentials plans, you can only add the integration from the Team Dashboard. Use the alternative instructions. To add an integration directly to a team, navigate to the Team Dashboard and open the Integrations tab. Click Add Integration and search for Sumo Logic and click add.

3. Click Save Integration.

Your configuration in Opsgenie should look something like the following:

Configuration in Sumo Logic

In Sumo Logic, scheduled searches send alerts to other tools via webhook connections. To send alerts from Sumo Logic to Opsgenie :

1. Create a Webhook Connection.
2. Once you set up the webhook connection, you'll have the option to use it in a Scheduled Search  or Monitor.

Create a Webhook Connection

note

You need the Manage connections role capability to create webhook connections.

This section demonstrates how to create a webhook connection from Sumo Logic to Opsgenie.

1. In Sumo Logic, go to Manage Data > Monitoring > Connections.
2. Click + Add and choose Opsgenie as the connection type.
   
3. Enter a Name and give an optional Description to the connection.
4. Paste the Integration Url from Opsgenie into the URL field.
5. (Optional) Enter an Authorization Header, which may include an authorization token.
6. (Optional) Custom Headers, enter up to five comma separated key-value pairs.
7. (Optional) Opsgenie uses the Priority value to define the priority of alerts. Edits to the Priority value are automatically updated in the JSON payload and vice versa.
8. The following JSON is the default Alert Payload, you can customize it as needed. For details on variables you can use as parameters within your JSON object, see Webhook Payload Variables.

   {
    "AlertName": "{{AlertName}}",
    "Description": "{{Description}}",
    "action": "create",
    "AlertURL": "{{AlertResponseURL}}",
    "Query": "{{Query}}",
    "QueryURL": "{{QueryURL}}",
    "TriggerTime": "{{TriggerTime}}",
    "TriggerTimeRange": "{{TriggerTimeRange}}",
    "TriggerCondition": "{{TriggerCondition}}",
    "TriggerValue": "{{TriggerValue}}",
    "TriggerType": "{{TriggerType}}",
    "ResultsJson": "{{ResultsJSON}}",
    "DetectionMethod": "{{DetectionMethod}}",
    "MonitorType": "{{MonitorType}}",
    "NumQueryResults": "{{NumQueryResults}}",
    "SourceURL": "{{SourceURL}}"
   }
9. In the Recovery Payload section, you can customize your recovery notification.
10. To test the connection, click Test Alert or Test Recovery. If successful, you'll see a 200 OK response message.
11. Click Save.