Docs
WebsiteLoginFree Trial
  • Getting Started
    • OnCall Users
    • Team Admins
    • Account Admins
  • Architecture Guide
  • Common UI Design Patterns
  • Alerts
  • Teams
  • Schedules
  • Escalation Policies
  • Integrations
  • Broadcasts
  • Users
  • Notifications
  • Reports
  • Billing
  • Accounts
  • Stakeholders
  • Maintenance Windows
  • Routers
  • Notification Rules
  • Single Sign On (SSO)
  • Integration Guides
    • Introduction
    • 66uptime
    • Apex Ping
    • AppDynamics
    • Auvik
    • AWS CloudWatch
    • Azure Monitor
    • Cloudflare
    • Cronitor
    • Datadog
    • Dead Man's Snitch
    • Echoes HQ
    • ElastAlert
    • Email
    • Form
    • Freshdesk
    • Freshservice
    • Google Hangouts Chat
    • Grafana
    • Healthchecks.io
    • HetrixTools
    • Honeybadger
    • Hydrozen
    • Jira Server
    • JotForm
    • Kapacitor
    • LogicMonitor
    • Mattermost
      • Outgoing Webhook
      • Post to Channel
    • Meta Workplace
    • Microsoft Teams
    • New Relic
    • Outgoing Webhook
    • Pingdom
    • Prometheus
    • PRTG Network Monitor
    • Pulsetic
    • Sentry
    • ServerGuard24
    • Site24x7
    • Slack
      • Notifications
      • Outgoing Webhook
      • Post to Channel
    • SolarWinds
    • Stackdriver
    • StatusCake
    • Twilio
      • Incoming SMS
      • Live Call Routing
    • Typeform
    • Uptime
    • Uptime Kuma
    • UptimeRobot
    • Webhook
    • Zendesk
  • API
    • Introduction
    • Authentication
    • Errors
    • Pagination and Filters
    • Common Model Attributes
    • Account Users
    • Alerts
    • Broadcasts
    • Comments
    • Escalation Policies
    • Events
    • Integrations
    • Logs
    • Maintenance Windows
    • Notification Rules
    • Routers
    • Schedules
    • Teams
    • Users
  • Command Line Interface (CLI)
    • PagerTree CLI: Command Line Interface
Powered by GitBook
On this page
  • What is SolarWinds?
  • How It Works
  • Integration Walkthrough
  • In PagerTree
  • In SolarWinds
  • Troubleshooting

Was this helpful?

  1. Integration Guides

SolarWinds

Connect your SolarWinds alerts to PagerTree.

PreviousPost to ChannelNextStackdriver

Last updated 11 months ago

Was this helpful?

Company
Estimated Time
Vendor Docs
Open Source

10 minutes

What is SolarWinds?

gives you the tools to monitor your applications and environment through a single web console.

How It Works

SolarWinds triggers user defined alerts when (configured) network events occur.

  • When an alert in SolarWinds is triggered, an alert is created in PagerTree automatically.

  • When an alert in SolarWinds is reset, the alert is resolved in PagerTree automatically.

Integration Walkthrough

In this integration tutorial we will show you how to send alerts from SolarWinds into PagerTree. The estimated time for this integration is 10 minutes. We assume that you already have a PagerTree account and SolarWinds installation setup.

In PagerTree

  1. by clicking the SolarWinds logo.

  2. .

In SolarWinds

  1. Navigate to Alerts & Activity -> Alerts.

  2. In the upper right hand corner, click the Manage Alerts button to go to the Alert Manager.

  3. In Alert Manager click Add New Alert.

  4. In the Add New Alert Wizard

    1. Properties

      1. Name of the alert definition - An appropriate name (e.g. High CPU)

      2. Choose the severity of the alert. (PagerTree automatically maps the SolarWinds severity to the PagerTree urgency)

      3. Click Next

    2. Trigger Condition

      1. Select conditions that will trigger an alert (create an alert)

      2. Click Next

    3. Reset Condition

      1. Select conditions that will reset and alert (resolve and alert)

      2. Click Next

    4. Time of Day

      1. Select time of day conditions (if only applicable during certain times)

      2. Click Next

    5. Trigger Action

      1. Message - Create an appropriate message (this will be displayed in the title of the alert created in PagerTree)

      2. Trigger Actions

        1. Click Add Action

        2. Select the Send a GET or POST Request to a Web Server option, then click Configure Action.

          1. Name of action - An appropriate name (e.g. PagerTree Trigger Action)

          2. Under HTTP request settings:

            1. Paste the PagerTree Endpoint URL you copied for the URL

            2. Select Use HTTP/S POST

            3. Click Add Action

          3. Click Next

        3. Reset Action

          1. Click Add Action

          2. Select the Send a GET or POST Request to a Web Server option, then click Configure Action.

            1. Name of action - An appropriate name (e.g. PagerTree Reset Action)

            2. Under HTTP request settings:

              1. Paste the PagerTree Endpoint URL you copied for the URL

              2. Select Use HTTP/S POST

              3. Click Add Action

            3. Click Next

            4. Summary

              1. Review all configuration details and if correct, click Submit

You have successfully completed the SolarWinds Integration.

SolarWinds Action Payload

solarwinds_action_payload.url

ActionType=Create&NodeName=${NodeName}&AlertID=${N=Alerting;M=AlertID}&AlertMessage=${N=Alerting;M=AlertMessage}&AlertDescription=${N=Alerting;M=AlertDescription}&AlertDetailsUrl=${N=Alerting;M=AlertDetailsUrl}&AcknowledgeUrl=${N=Alerting;M=AcknowledgeUrl}&AlertTriggerCount=${N=Alerting;M=AlertTriggerCount}&AlertTriggerTime=${N=Alerting;M=AlertTriggerTime;F=DateTime}&Severity=${N=Alerting;M=Severity}

If you prefer JSON, make sure to set the Content-Type to "application/json" and use this body payload instead:

solarwinds_action_payload.json
{
    "ActionType": "Create",
    "NodeName": "${NodeName}",
    "AlertID": "${N=Alerting;M=AlertID}",
    "AlertMessage": "${N=Alerting;M=AlertMessage}",
    "AlertDescription": "${N=Alerting;M=AlertDescription}",
    "AlertDetailsUrl": "${N=Alerting;M=AlertDetailsUrl}",
    "AcknowledgeUrl": "${N=Alerting;M=AcknowledgeUrl}",
    "AlertTriggerCount": "${N=Alerting;M=AlertTriggerCount}",
    "AlertTriggerTime": "${N=Alerting;M=AlertTriggerTime;F=DateTime}",
    "Severity": "${N=Alerting;M=Severity}"
}

SolarWinds Reset Payload

solarwinds_reset_payload.url
ActionType=Resolve&AlertID=${N=Alerting;M=AlertID}

If you prefer JSON, make sure to set the Content-Type to "application/json" and use this body payload instead:

{
    "ActionType": "Resolve",
    "AlertID": "${N=Alerting;M=AlertID}"
}

Troubleshooting

If you don't see integration logs being generated on the PagerTree side, check the SolarWind log files. Customers with self-managed instances have reported the following types of errors:

  • Invalid Root Certificates (TLS)


Body to POST - copy and paste the

Body to POST - copy and paste the

solarwinds_action_payload (below)
solarwinds_reset_payload (below)
SolarWinds Worldwide, LLC
view
v3.rb
SolarWinds
Create the integration
Copy the Endpoint URL
SolarWinds Alert Properties
SolarWinds Trigger Condition
SolarWinds Reset Condition
Solarwinds Time of Day
Solarwinds PagerTree HTTP/S action configuration.
Solarwinds PagerTree Reset Action
Review alert configuration
SolarWinds Alert Properties
SolarWinds Trigger Condition
SolarWinds Reset Condition
Solarwinds Time of Day
Solarwinds PagerTree HTTP/S action configuration.
Solarwinds PagerTree HTTP/S action configuration.
Solarwinds PagerTree Reset Action
Review alert configuration