• Get started
  • Documentation

Integrate Opsgenie with Server Density

Server Density logo

What does Opsgenie offer Server Density users?

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

Functionality of the integration

  • When an alert is created on Server Density, an alert is created on Opsgenie automatically through the integration.

  • When the alert is closed on Server Density, the related alert is also closed on Opsgenie

Add Server Density integration to Opsgenie

Basic Configuration

Opsgenie’s Server Density integration provides sensible defaults. Basic configuration settings contain the minimum configuration information required to make the integration work.

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 Server Density and select Add

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

  3. Copy the integration URL which includes the Opsgenie endpoint as well as the API key.

  4. Select Save Integration.

Configuring a Webhook in Server Density

  1. In Server Density, go to "Preferences" under your profile.

Server Density Notifications

2. Select the "Notifications" tab, then select "Webhooks". Paste the URL copied from the Opsgenie Server Density integration page into the URL field. Add the webhook by clicking on the plus sign.

3. Now that the webhook is configured, configure Server Density alerts to notify via the "Opsgenie Webhook" just created.

4. Go to the Services/Devices Dashboard, Alerting tab and open "configure alerts" page for an item.

Server Density services

5. From the recipients, find "Opsgenie Webhook" and click to enable it.

Server Density service alerts

Advanced Configuration Settings

Opsgenie’s Server Density integration uses sensible configuration defaults to make the integration as easy as possible. However, it is also possible to customize the integration. Advanced settings allow:

  • Defining different rules to notify different people for different alerts

  • Modifying 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

Server Density alert filters

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.

Server Density action fields

Sample payload sent from Server Density

Sample

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.