Skip to main content

Pingdom Webhook

Configure a Pingdom webhook endpoint to create incidents in Cloudaware from Pingdom alerts.

info
  • Audience: Cloudaware administrators, SRE teams, NOC teams, and monitoring teams
  • Outcome: Pingdom alerts are sent to Cloudaware as incidents for routing, CMDB context, and reporting

Capabilities​

The integration supports:

  • Pingdom alerts received as Cloudaware incidents
  • Relationship mappings between Pingdom incidents and related assets in the CMDB
  • Search and reporting for Pingdom webhook incidents using CMDB Navigator, CMDB list views, and reports

Prerequisites​

Before you begin, make sure you have:

  • Access to a Cloudaware account.
  • A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
  • Pingdom checks that should send alerts to Cloudaware.

Add a Pingdom Webhook Endpoint to Cloudaware​

  1. In Cloudaware, go to Admin Console.
  2. Find Pingdom Webhook, then click + ADD.
  3. Enter a descriptive name for the webhook endpoint.
  4. Click Save to generate the webhook URL.
  5. In Pingdom, add a Webhook integration and paste the Cloudaware webhook URL.
  6. Assign the webhook to the relevant checks and send a test alert.
tip

Test the webhook with a limited set of checks before assigning it broadly.

View Pingdom Webhook Data in CMDB​

  1. In Cloudaware, open CMDB Navigator.
  2. In the left pane, select PINGDOM WEBHOOK.
  3. Open the incident or related monitoring object list to view Pingdom alert records.

Troubleshooting​

note

Webhook-triggered incidents depend on the Pingdom webhook assignment, check state, and Cloudaware endpoint availability.

Pingdom Alerts Do Not Create Cloudaware Incidents​

  • Confirm that the Pingdom Webhook endpoint is configured in Cloudaware.
  • Verify that the Pingdom webhook integration uses the current Cloudaware webhook URL.
  • Check that the webhook is assigned to the relevant Pingdom checks.
  • Send a test alert from Pingdom and review the result.

Incidents Are Missing or Delayed​

  • Confirm that Pingdom generated an alert for the check.
  • Verify that the Cloudaware webhook endpoint is active.
  • Review Pingdom webhook delivery results for errors.
  • In CMDB Navigator, verify that you are viewing the PINGDOM WEBHOOK section and related resources.

Webhook URL Errors Are Displayed​

  • Verify that the Cloudaware webhook URL was copied correctly.
  • Regenerate or update the webhook endpoint if the URL changed.
  • Reassign the updated webhook URL to the affected Pingdom checks.

Still stuck? Contact Cloudaware Support at support@cloudaware.com with the integration name and a brief description of the issue.

Reconfigure or Remove the Integration​

warning

To update the webhook URL or check assignment, edit the existing integration and Pingdom webhook settings instead of deleting and re-creating it.

Update the Integration Details​

  1. Go to Admin.
  2. Select Pingdom Webhook.
  3. Select the specific integration.
  4. Open the three-dot menu (⋮), then click Edit.
  5. Update the required fields.
  6. Click Save.

Remove the Integration from Cloudaware​

  1. Go to Admin.
  2. Select Pingdom Webhook.
  3. Select the specific integration.
  4. Open the three-dot menu (⋮), then click Delete.
  5. Confirm the deletion if prompted.

Security Notes​

  • Treat the generated webhook URL as sensitive and avoid sharing it through tickets, chat, or documentation.
  • Assign the webhook only to Pingdom checks that should create incidents in Cloudaware.
  • Review Pingdom webhook assignments regularly to confirm that they match the intended monitoring scope.
  • Regenerate or replace the webhook URL if it is exposed or no longer trusted.
  • Remove unused webhook assignments in Pingdom when the Pingdom Webhook integration is removed from Cloudaware.