• Products
  • Get started
  • Documentation
  • Resources

Integrate Opsgenie with DripStat

DripStat logo

​What does Opsgenie offer to Dripstat users?

Use Opsgenie’s Dripstat integration to send Dripstat alerts to Opsgenie API with detailed information. Opsgenie acts as a dispatcher for Dripstat alerts, determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, and iPhone & Android push notifications, and escalates alerts until the alert is acknowledged or closed.

Functionality of the integration

  • When alert is created on Dripstat, an alert is created in Opsgenie automatically through the integration.

Add Dripstat integration in Opsgenie

If you're using Opsgenie's Free or Essentials plan or if you’re using Opsgenie with Jira Service Management's Standard plan, you can add this integration from your team dashboard only. The Integrations page under Settings is not available in your plan.

  1. Go to Teams and select your team.

  2. Select Integrations on the left navigation and then select Add integration.

Adding the integration from your team dashboard will make your team the owner of the integration. This means Opsgenie will assign the alerts received through this integration to your team only. Follow the rest of the steps in this section to set up the integration.

  1. Go to Settings > Integrations. Search for Dripstat and select Add

  2. Specify who is notified of Dripstat alerts using the Responders field. Auto-complete suggestions are provided as you type.

  3. Copy the integration API key. Use this key in Dripstat configuration.

  4. Select Save Integration.

Configuration on Dripstat

  1. In Dripstat, go to the Alerts page.

  2. Select "Integrations tab".

  3. Click on Opsgenie.

  4. Select "Opsgenie" as the action type.

  5. Paste the API key you copied into the "API Key" field.

  6. Click Save.

Dripstat connect to Opsgenie

Dynamic fields (custom priority, payload, url, and headers) are not available for this integration because of being API-based integration.


Additional Help