SolarWinds Pingdom Transaction Checks API poller template

Use this SAM API poller template to monitor SolarWinds Pingdom counters for transaction checks on websites monitored by Pingdom.

Prerequisites

• Use the following parameters to specify the API endpoint in the request URL:
• ${API_PINGDOMTAG}
• ${API_CHECKID}
• ${API_TEAMID}
• ${API_CONTACTID}
• A Bearer Token is provided in header. See API poller authorization

Notes

• Default thresholds are not set for this template.
• For reference, see Welcome to the Pingdom API.
• Here are some API request examples:
  • https://api.pingdom.com/api/3.1/tms/check?tags=${API_PINGDOMTAG}
  • https://api.pingdom.com/api/3.1/tms/check/${API_CHECKID}
  • https://api.pingdom.com/api/3.1/alerting/contacts/${API_CONTACTID}
• String-based metrics (for example, team names) are returned as arrays of comma-separated integers.

Available metrics

Status code for TMS checks

The status code returned by a successful API request is defined in the documentation for that method. Usually, this will be 200 OK. If something goes wrong, other codes may be returned. The API uses standard HTTP/1.1 status codes defined by RFC 2616.

Unit: Status code

TMS checks API response time (ms)

The response time (in milliseconds).

Unit: Milliseconds

All checks for specified tag(s)

The number of TMS checks for the specified tag

Unit: Count

All teams to alert for specified check

The teams to alert, represented by comma-separated integers.

Unit: Array of integers

All contacts to alert for specified check

The contacts to alert.

Unit: Array of integers

All teams

The number of teams.

Unit: Count

All team members for specified team

The list of members of the specified team.

Unit: Array of integers

All SMS associated with the specified contact

The list of SMS objects associated with the specified contact.

Unit: Array of integers

All emails associated with the specified contact

The list of email objects associated with the specified contact.

Unit: Array of integers