• Products
  • Get started
  • Documentation
  • Resources

Integrate with Pingdom Server Monitor

If you’re a customer who shifted your operations from Opsgenie to Jira Service Management, adding new instances of this integration isn’t possible in Jira Service Management. You can only edit the integrations that originally shifted from Opsgenie.

Pingdom logo

SolarWinds Pingdom Server Monitor system allows developers to create plugins to extend its functionality, monitor any application and system resource, and trigger alerts to notify relevant people when necessary. Pingdom Server Monitor cannot only alert for typical server problems, simple thresholds, etc. but also can do sophisticated trending, detect relative changes etc.

What does Jira Service Management offer Pingdom Server Monitor users?

Stay connected with mobile

Use Jira Service Management to receive notifications for critical Pingdom Server Monitor alerts via SMS, phone calls, and iOS & Android push notifications, and to respond to the alerts directly from mobile devices using the Jira mobile app.

Consolidate alert & notification management

Pingdom Server Monitor users leverage Jira Service Management to aggregate and manage alerts not only from Pingdom Server Monitor but also from other sources. Jira Service Management enables users to maintain their own notifications information and preferences, eliminating the burden to keep this information current and accurate in multiple disparate tools.

Alert lifecycle management

For Pingdom Server Monitor users, the Jira Service Management integration provides full alert lifecycle management capabilities. Use Jira Service Management to not only receive notifications for critical problems detected by Pingdom Server Monitor, but also rapidly acknowledge alerts, take or assign ownership of the alerts, comment on them, and more, no matter when and where the alerts are received. Jira Service Management keeps track of all alert activity seamlessly: when the alert was created, who was notified when and how, whether and when recipients have seen the alert, acknowledged it, and who executed which action. Jira Service Management automatically closes alerts when the host/service comes back up.

Alerts that empower

A short text message (SMS) typically used to notify users often fails to convey sufficient information to enable recipients to assess the problem and determine the right course of action. Jira Service Management alerts are not limited to couple hundred characters of text, includes many fields, tags, and attached files. Recipients can not only see the alert message, but all the supporting information and chart to figure out what to do next. Attach any relevant information to the alert and make it available to the recipients, either via the API or the web UI.

Functionality of the integration

  • When an alert is created in Pingdom Server Monitor, an alert is created in Jira Service Management.

  • When an alert is closed in the Pingdom Server Monitor, the alert is closed in Jira Service Management.

Edit Pingdom Server Monitor integration in Jira Service Management

To edit a Pingdom Server Monitor 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.

  3. Search for your Pingdom Server Monitor integration.

  4. Edit the integration settings and rules as necessary.

Configure the integration in Pingdom Server Monitor

Use the instructions in this section if applicable.

  1. Go to the "Notifications" page.

Pingdom Server Monitor Notification

2. In "Notification Channels", click Add OpsGenie.

Pingdom Server Monitor Notification Channels

3. Paste the integration API key from Jira Service Management into the "API Key" field, set the teams (optional), and click Submit.

Pingdom Server Monitor API

4. Go back to the "Notifications" page, and add Jira Service Management to the relevant Notification Groups.

Advanced Configuration Settings

Jira Service Management's Pingdom Server Monitor 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 Pingdom Server Monitor webhook payload

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

  • Lifecycle

  • Severity

  • Metric Name

  • Metric Value

  • Plugin Name

  • Server Host Name

  • Server Name

  • Time

  • Title

  • URL

  • Metric Chart URL

Pingdom Server Monitor Filter Variables

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

Pingdom Server Monitor alert fields

Sample payload sent from Pingdom Server Monitor


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 { "event_name": "new_item", "data": { "item": { "public_item_id": null, "integrations_data": {}, "last_activated_timestamp": 1390917586, "hash": "1cbf07b5da947216f68ea8b8dd4813fa43317b90", "id": 274146948, "environment": "staging", "title": "ReferenceError: Uncaught ReferenceError: testing_rollbar_123 is not defined", "last_occurrence_id": 770525810, "last_occurrence_timestamp": 1390917588, "platform": 1, "first_occurrence_timestamp": 1390917586, "project_id": 6869, "resolved_in_version": 6, "status": 1, "unique_occurrences": null, "framework": 7, "total_occurrences": 1, "level": 40, "counter": 1, "first_occurrence_id": 770525810, "activating_occurrence_id": 770525810 } } }


Still need help?

The Atlassian Community is here for you.