How to Integrate Prometheus Alertmanager with Pingzo

Prometheus is the core metrics collection engine for Kubernetes clusters and containerized applications. While Prometheus gathers rich performance data and Alertmanager evaluates alerting rules, delivering these notifications to the right chat platforms can be difficult. By connecting Prometheus Alertmanager to Pingzo, you can route container alerts to developer chat channels instantly.

This guide details how to configure Alertmanager to send alert payloads to Pingzo's webhook gateway.

Why Route Prometheus Alerts to Pingzo?

• Native WhatsApp Support: Deliver server, memory, and database alerts directly to developers' phones using official WhatsApp notifications.
• Intelligent Alert Grouping: Pingzo groups related Prometheus alerts to prevent notification storms when a Kubernetes node drops.
• Simple Setup: Bypasses complex Alertmanager configuration rules for chat integrations, utilizing Pingzo's managed webhook routes.
• Unified Monitoring Board: Centralize internal container alerts alongside external public status page monitoring checks.

Configuration Steps

Follow these steps to establish a connection between Prometheus Alertmanager and Pingzo:

Step 1: Generate a Custom Webhook in Pingzo

1. Log in to your Pingzo Dashboard and open the Alert Channels page.
2. Click Add Channel and choose Custom Webhook from the list.
3. Assign the channel a name (e.g., "Prometheus Alertmanager Gateway").
4. Copy the generated Webhook Endpoint URL.
5. Click Save.

Step 2: Configure Prometheus Alertmanager config.yml

Update your Alertmanager configuration file to register Pingzo as a webhook receiver:

1. Open your alertmanager.yml configuration file.
2. Under the receivers section, add a new webhook receiver:

   receivers:
     - name: 'pingzo-webhook'
       webhook_configs:
         - url: 'https://api.pingzoapp.com/v1/webhooks/your-custom-webhook-id'
           send_resolved: true
   

   Replace the URL with the Webhook Endpoint URL you copied in Step 1.
3. Under the route section, map your alerts to this receiver:

   route:
     group_by: ['alertname', 'cluster', 'service']
     group_wait: 30s
     group_interval: 5m
     repeat_interval: 4h
     receiver: 'pingzo-webhook'
   

4. Save the configuration file.

Step 3: Apply and Restart Alertmanager

Apply the updated configuration by reloading Alertmanager:

1. If running in a Docker or Kubernetes environment, reload the config configmap or run an HTTP reload command:

   curl -X POST http://localhost:9093/-/reload
   

2. If running Alertmanager as a systemd service, restart it:

   sudo systemctl restart alertmanager
   

Verify Alert Delivery

To verify that Alertmanager is correctly forwarding alerts to Pingzo:

1. Simulate a system alert using Prometheus Alertmanager's CLI tool (amtool) or trigger a mock rule (like setting CPU load threshold low).
2. Check your connected Pingzo endpoints (such as WhatsApp, Discord, or Telegram) to verify that the alert arrives.
3. Check that the incident details (such as alert name, description, and severity) are formatted cleanly.
4. Confirm that Alertmanager dispatches a recovery payload when the trigger condition resolves, automatically clearing the incident.