Get started with Opsgenie as a user
Learn how to configure your profile, get notifications from Opsgenie and view on-call schedules.
Integrate Opsgenie with Sensu
What does Opsgenie offer to Sensu users?
Sensu sends notifications of new events. With a Sensu Integration, Opsgenie acts as a dispatcher for these 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 an alert is created on Sensu, an alert is created in Opsgenie automatically through the integration.
Add Sensu 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.
Go to Teams and select your team.
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.
Go to Settings > Integrations. Search for Sensu and select Add.
Specify who is notified of Sensu alerts using the Responders field. Auto-complete suggestions are provided as you type.
Copy the API Key.
Select Save Integration.
Configuration in Sensu
Sensu Enterprise 3.0 updates the Opsgenie integration to use Opsgenie’s new v2 Alert API, necessitating a breaking change to Sensu Enterprise’s Opsgenie configuration specification.
Instructions have been updated accordingly.
Sensu has a plugin to create and close alerts in Opsgenie.
Install Sensu's Opsgenie Plugin.
Configure Sensu to use Opsgenie’s plugin.
The plugin uses a json file as configuration. Escalations and teams are translated to the "responders" attribute, as shown below.
5. In the configuration file, populate the "api_key" field with the API Key copied previously.
6. Populate responders to add them to the created alert.
Sensu Enterprise 3.0 updates the name of the /overwrites_quiet_hours/ attribute to /overwrite_quiet_hours/. The singular form of this attribute is required to achieve the desired result of overriding alert filtering that would otherwise prevent Opsgenie from notifying recipient(s) during their configured quiet hours.
Was this helpful?
Still need help?
The Atlassian Community is here for you.