Dozzle
Dozzle alerts when a container’s log matches a pattern, when its CPU or memory crosses a threshold, or on a Docker event. Give it an InfraInbox webhook and each alert arrives as an event, on the destinations you choose, with routing, quiet hours and re-notify on top.
Tested with: built from Dozzle 10’s webhook documentation; not yet run against a live Dozzle.
What you get
Section titled “What you get”Each Dozzle alert is one WARNING event, titled with the container and the alert’s name, with the matched log line or metric values as its body. Repeats of the same alert on the same container group into one incident.
Dozzle sends no “back to normal” message, so these incidents close after 24 hours without a repeat, or when you resolve them.
Prerequisites
Section titled “Prerequisites”- Dozzle 10 or later, with its
/datadirectory on a volume so its notification settings survive a restart. - An InfraInbox address Dozzle can reach that isn’t
localhostor127.0.0.1: Dozzle refuses to send webhooks to loopback addresses.
-
Go to Add source → Dozzle and name it. InfraInbox issues a key for the URL, shown once, with the webhook URL filled in.
-
In Dozzle, open Notifications and add a destination:
Field Value Type Webhook URL https://infrainbox.example.com/hooks/generic/iik_src_…Template Custom -
Paste this template:
{"title": "{{.Container.Name}}: {{.Subscription.Name}}","severity": "warning","type": "dozzle.alert","resource": "container:{{.Container.Name}}","dedupKey": "dozzle:{{.Container.HostName}}:{{.Container.Name}}:{{.Subscription.Name}}","body": "{{.Detail}}"} -
Click Test. The source shows Receiving events. If the test opened an incident, resolve it.
-
Create or edit your Dozzle alerts and send them to this destination.
The URL, with a placeholder where the key goes, stays on the source’s Connect tab.
Limitations
Section titled “Limitations”- Every alert arrives as WARNING. To make some louder, add a routing rule on the
dozzle.alerttype and the alert’s name in the title. - A body InfraInbox can’t read (a template edited into invalid JSON, say) is still kept, as an unparsed event you can open.
- Routing rules — route by container or alert
- Events API — the fields the template fills in