Komodo

Coming soon. Pinglet’s server-side translation (?rewrite=komodo) is built and live, but Komodo’s Custom alerter can’t yet attach the Authorization header a publish needs — that requires an upstream change to Komodo (feature request). This page describes how the integration will work once it lands.

Komodo will be able to deliver its alerts — CPU/memory/disk thresholds, container and stack state changes, build and procedure failures, image updates — to a Pinglet topic via a Custom alerter. Add ?rewrite=komodo to the publish URL and Pinglet translates Komodo’s alert payload into a native push.

Can’t wait? Put a reverse proxy or tiny relay in front of Pinglet that injects the Authorization header, and point Komodo’s Custom alerter at that — see Generic webhook. Everything below works today through such a relay.

Setup

In Komodo, create an alerter with the Custom endpoint type:

Replace acme/komodo with your namespace and preferred topic name — the topic is created on the first alert. Subscribe to it in the Pinglet app via the share link from your dashboard.

What you’ll receive

Komodo’s severity maps to the message’s level and priority:

Each alert type renders as a readable sentence — e.g. a ServerCpu alert becomes a CPU-percentage message for the named server, a ContainerStateChange reports the container’s new state, and resolved alerts are titled Resolved: <alert>. Unknown or new Komodo alert variants still come through with a sensible generic title, so a Komodo upgrade won’t silently drop alerts.

The target’s resource type and the alert’s scalar context are attached as metadata (shown on Pro plans), with at-a-glance values as card badges.

Only an unresolved CRITICAL is urgent. Warnings, test pings and resolutions arrive as standard notifications.