Pingdom Integration

Connect ReliaPulse to Pingdom to import your existing uptime checks and display their status.

Prerequisites

• Pingdom account (any plan)
• API Token with read access
• Existing checks configured in Pingdom

Configuration

Create Integration

1. Go to Dashboard → Settings → Integrations
2. Click Add Integration
3. Select Pingdom
4. Fill in the configuration:

Generate API Token

1. Log in to Pingdom
2. Go to Settings → Pingdom API
3. Click Add API token
4. Give it a name and select Read access
5. Copy the token to ReliaPulse

Importing Checks

Available Check Types

ReliaPulse can import:

• HTTP/HTTPS checks
• TCP checks
• DNS checks
• Ping (ICMP) checks

Sync Behavior

When you create a Pingdom integration:

1. ReliaPulse fetches all your Pingdom checks
2. Creates corresponding metrics queries
3. Polls status periodically based on your configured interval

Check Status Mapping

Creating Metrics Queries

Query Configuration

For Pingdom, queries reference check IDs:

Finding Check IDs

1. In Pingdom, go to Uptime → Checks
2. Click on a check
3. The URL contains the check ID: /checks/12345678

Bulk Import

You can import all checks at once:

1. In the integration settings, click Import All Checks
2. Select which checks to import
3. ReliaPulse creates metrics queries for each

Displaying Check Data

Status Display

Pingdom checks show:

• Current status (up/down)
• Response time
• Last check time
• Uptime percentage

Linking to Components

Connect Pingdom checks to components:

1. Edit a component
2. Set type to METRIC
3. Select your Pingdom integration
4. Choose the check to monitor

Status Page Widgets

Use the Metrics widget type to display:

• Check status indicator
• Response time chart
• Uptime percentage

Multi-Check Monitoring

Grouping Checks

Organize multiple Pingdom checks:

1. Create a component group in ReliaPulse
2. Create child components linked to individual checks
3. Parent status reflects worst child status

Aggregate Views

For overview dashboards:

• Use Infrastructure Table widget
• Shows all checks with status bars
• Drill down to individual check details

Threshold Configuration

Configure when to trigger alerts:

Troubleshooting

Authentication Failed

• Verify API token is correct
• Check token has not expired
• Ensure token has read permissions

Checks Not Appearing

• Verify checks exist in Pingdom
• Check token has access to the checks
• Refresh the integration

Status Not Updating

• Check polling interval
• Verify Pingdom API is accessible
• Check ReliaPulse logs for errors

Incorrect Status

• Pingdom has confirmation periods for status changes
• Status may lag by a few minutes
• Check Pingdom's native UI for current status

Best Practices

Check Organization

• Name checks clearly in Pingdom
• Use consistent naming conventions
• Group related checks by service

Polling Intervals

• Match or exceed Pingdom's check interval
• Avoid polling more frequently than Pingdom checks
• Consider API rate limits

Threshold Alignment

• Align ReliaPulse thresholds with Pingdom alerts
• Avoid duplicate alerting (use one or the other)
• Configure appropriate notification channels

Limitations

• Read-only integration (can't create checks in Pingdom)
• Status is polled, not pushed (slight delay)
• Response time is from Pingdom's perspective
• Historical data limited to Pingdom's retention

Related

• Prometheus Integration
• Metrics Overview
• Components