• Products
  • Get started
  • Documentation
  • Resources

Integrate with Server Density

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.

Server Density logo

What does the integration offer?

Server Density alerts are seamlessly integrated with Jira Service Management using Server Density's webhook alert notifications. The integration enables customers to forward Server Density alerts to Jira Service Management and take advantage of Jira Service Management's extensive alert & notification management, on-call scheduling, and escalation capabilities.

How does the integration work?

  • When an alert is created on Server Density, an alert is created on Jira Service Management automatically through the integration.

  • When the alert is closed on Server Density, the related alert is also closed on Jira Service Management

Set up the integration

Server Density is an API integration. Setting it up involves the following steps:

  • Add a Server Density integration in Jira Service Management

  • Configure the integration in Server Density

Add a Server Density integration

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 Server Density integration in Jira Service Management, complete the following steps:

  1. Go to your team’s operations page.

  2. On the left navigation panel, select Integrations and then Add integration.

  3. Run a search and select “Server Density”.

  4. On the next screen, enter a name for the integration.

  5. Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.

  6. Select Continue.
    The integration is saved at this point.

  7. Expand the Steps to configure the integration section and copy the integration URL and the API key.
    You will use this key while configuring the integration in Server Density later.

  8. Select Turn on integration.
    The rules you create for the integration will work only if you turn on the integration.

Configure the integration in Server Density

To configure the integration of Server Density with Jira Service Management, complete the following steps:

  1. In Server Density, select Preferences under your profile.

  2. Go to Notifications > Webhooks.

  3. Enter a name for the webhook.

  4. Paste the integration URL copied previously into URL and select +.
    Now that the webhook is configured, you can configure Server Density alerts to notify via the "Opsgenie Webhook" just created.

  5. Go to the Services or Devices dashboard and open the Alerting tab.

  6. Configure the webhook you created as the alert responder.

The Server Density integration uses sensible configuration defaults to make the integration as easy as possible. However, it is also possible to customize the integration to:

  • Define different rules to notify different people for different alerts

  • Modify alert content using Server Density webhook payload

The following variables from Server Density alert webhook payload are available when defining filters and when setting the alert fields values:

  • Incident Id

  • Alert Id

  • Item Type

  • Item Name

  • Alert Section

  • Alert Type

  • Current Value

  • Trigger Datetime

  • Trigger Value

  • Fixed

Create multiple rules with filters using the variables from Server Density webhook payload. For each rule, alert fields can have different values, hence different people can be notified and alerts can have different tags.

Sample payload sent from Server Density


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 { "alert_id": "52d575043012a5962c8b4569", "incident_id": "52d575043012a5962c8b4569", "alert_section": "http", "alert_type": "status", "configured_trigger_value": "up", "configured_trigger_location_threshold": 1, "current_value": { "Spain: Madrid": "up", "Australia: Sydney": "up", "Singapore": "up" }, "item_cloud": false, "item_id": "52dd4b7395fe35a106000000", "item_name": "opsgenie", "item_type": "Service", "trigger_datetime": "2014-01-21 07:35:42", "fixed": false }





Still need help?

The Atlassian Community is here for you.