docs

AWS, Google Cloud and Azure

Send your cloud alerts to your phone: CloudWatch alarms through Amazon SNS, Google Cloud Monitoring incidents, and Azure Monitor alerts. When the problem clears, the alert closes on its own.

Each cloud gets its own URL with your key in it. Cloud consoles don't always let you set headers, so the key goes in the URL, or as the password in https://x:YOUR_KEY@....

AWS: CloudWatch alarms via SNS

  1. In Amazon SNS, open the topic your CloudWatch alarms notify (or create one and pick it in the alarm's Notification settings for both In alarm and OK).

  2. Create subscription → Protocol HTTPS → Endpoint:

    https://api.zapapush.com/integrations/aws/YOUR_KEY

  3. Leave Enable raw message delivery off. ZapaPUSH confirms the subscription by itself within a few seconds, and its status changes to Confirmed.

CloudWatch state In ZapaPUSH
ALARM Alert titled with the alarm name, with the reason and the metric. Buzzes your phone.
OK Closes it, silently.
INSUFFICIENT_DATA Ignored.

Other messages on the topic (not CloudWatch alarms) become alerts too, titled with the SNS Subject.

Google Cloud Monitoring

  1. Monitoring → Alerting → Edit notification channels → Webhooks → Add new.

  2. Endpoint URL:

    https://api.zapapush.com/integrations/gcp?auth_token=YOUR_KEY

    Or choose Use HTTP Basic Auth, with any username and your key as the password, and the URL https://api.zapapush.com/integrations/gcp.

  3. Test connection, then add the channel to your alerting policies.

An open incident becomes an alert titled policy: resource, for example Monitor-Project-Cluster: gke-cluster-1-default-pool, with the summary, the documentation, and the observed value against the threshold. A closed incident closes it, silently.

Azure Monitor

  1. Monitor → Alerts → Action groups → create or edit one → Actions → Webhook.

  2. URI:

    https://api.zapapush.com/integrations/azure/YOUR_KEY

  3. Set Enable the common alert schema to Yes. ZapaPUSH reads only the common schema.

  4. Add the action group to your alert rules.

Fired becomes an alert titled [severity] rule: resource, for example [Sev3] High CPU: vm-web-1, with the metric, operator, threshold and value, and the custom properties. Resolved closes it, silently.

Limits

  • Each notification counts as one post towards the 60-per-minute limit.
  • A request without a key gets 401 with a Basic auth challenge, which some clouds wait for before sending the password. An unknown key gets 404.