Komodo

Komodo can 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 URL and Pinglet translates Komodo’s alert payload into a native push.

Komodo’s Custom alerter can’t attach an Authorization header, so it posts to your topic’s link instead of using an API key.

Setup

Create the topic in your dashboard, for example komodo, and open its Settings.
Under Posting with the topic link, turn on Anyone with the link can post. Turn on Allow urgent posts too if you want CRITICAL alerts to break through Do Not Disturb.
Copy the topic link shown there. It looks like https://pinglet.dev/acme/komodo/k7f3x9q2.
In Komodo, create an alerter with the Custom endpoint type and set its endpoint to that link with ?rewrite=komodo on the end:

https://pinglet.dev/acme/komodo/k7f3x9q2?rewrite=komodo

No headers are needed. Subscribe to the topic in the Pinglet app with the same link.

The topic link is both the subscribe link and, with this setting on, the post link. Anyone you’ve shared it with can post to the topic, and those posts count toward your monthly notifications. If that matters, keep a dedicated topic for Komodo and share it only with the people who should get the alerts.

What you’ll receive

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

Komodo alert	Level	Priority
`CRITICAL`	`error`	`urgent`: breaks through DND
`WARNING`	`warning`	`normal`
`OK` / other	`info`	`normal`
Resolved (any severity)	`success`	`normal`

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, and only when Allow urgent posts is on; otherwise it arrives as a standard notification. Warnings, test pings and resolutions always arrive as standard notifications.