Integration · Web & proxy
Caddy
Per-host metrics, ACME certificates, plugin stack.
What gets collected
The Caddy admin API plus the metrics endpoint. Certificate expiry is tracked automatically.
Requirements
- ✓Caddy 2.x
- ✓admin API :2019
- ✓metrics enabled (default)
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
caddy.request.durationcaddy.cert.notaftercaddy.upstream.healthcaddy.requests.per_hostSetup steps
- 1
admin :2019 - 2
metrics enabled by default
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
Caddy
Frequently asked questions
- What does Unimoni collect from Caddy?
- Per-host metrics, ACME certificates, plugin stack. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Caddy and everything else in one place.
- How long does it take to connect Caddy?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the Caddy integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is Caddy monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.