Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.
Use Jira Service Management's Consul integration to sends Consul alerts to Jira Service Management API with detailed information. Jira Service Management acts as a dispatcher for Consul 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.
When Consul triggers an alert, an alert is created in Jira Service Management automatically through the integration.
Consul is an API-based integration. Setting it up involves the following steps:
Add a Consul integration in Jira Service Management
Configure the integration in Consul
Bidirectional integrations aren’t supported in Free and Standard plans. All the other integrations are supported at a team level in Free and Standard; however, for their outgoing part to work, you need to upgrade to a higher plan. To add any integration at a site level through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be either on Premium or Enterprise.
Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management only assigns the alerts received through this integration to your team.
To add a Consul integration in Jira Service Management, complete the following steps:
Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “Consul”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.
Expand the Steps to configure the integration section and copy the API key.
You will use this key while configuring the integration in Consul later.
Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
To configure the integration of Consul with Jira Service Management, complete the following steps:
1. Install Consul-Alerts on your Consul server. Find out how to install Consul-Alerts.
2. Ensure that Consul-Alerts is running.
3. Configure the Jira Service Management API key:
curl -X PUT -d 'API_KEY' http://localhost:8500/v1/kv/consul-alerts/config/notifiers/opsgenie/api-key
The Consul agent's IP and port may vary.
4. Optional: Set the entity field value to show up in Jira Service Management alert details. The default is 'Cluster-Alert'.
curl -X PUT -d 'Consul' http://localhost:8500/v1/kv/consul-alerts/config/notifiers/opsgenie/cluster-name
5. Enable Jira Service Management notifications in Consul-Alerts:
curl -X PUT -d 'true' http://localhost:8500/v1/kv/consul-alerts/config/notifiers/opsgenie/enabled
When a Consul healthcheck becomes critical, a Jira Service Management alert is automatically created. When the Consul healthcheck passes again, the Jira Service Management alert is automatically closed.
This is an API-based integration, so dynamic (draggable) properties such as custom priority, payload, URL, and headers aren't available.
Was this helpful?