Pingdom → Zabbix

Overview

This project integrates Pingdom checks into Zabbix via API, mapping checks to hosts and triggers to provide a single source of truth during incidents. Engineers no longer need to switch contexts to correlate external uptime with internal metrics.

The Problem

When investigating incidents, teams often had to check multiple dashboards — Pingdom for external uptime, Zabbix for internal metrics. This context-switching slowed down root cause analysis and made it harder to see the full picture.

The Solution

• Idempotent sync to avoid duplicates and noisy items
• Clear host/group mapping and templated triggers
• Smoother incident flow by reducing context switching
• Single pane of glass for both internal and external monitoring

How It Works

A Python script runs on a schedule, pulling check status from Pingdom's API and pushing it to Zabbix as trapper items. The script handles:

• Authentication with both APIs
• Mapping Pingdom checks to Zabbix hosts
• Creating/updating items and triggers automatically
• Handling API rate limits gracefully