1. Output of caddy version:
$ caddy version
v2.5.2 h1:eCJdLyEyAGzuQTa5Mh3gETnYWDClo1LjtQm2q9RNZrs=
2. How I run Caddy:
a. System environment:
Directly on Debian GNU/Linux 11 (bullseye) with Systemd.
b. Command:
automatically via systemd
c. Service/unit/compose file:
Main Caddyfile
import {{ caddy_sites_conf_dir }}/*.caddyconf
First imported file
neururer.pjsmets.com
{
encode zstd gzip
root * /var/www/neururer.pjsmets.com/html
file_server
}
Second imported file
www.pjsmets.com, pjsmets.com
{
encode zstd gzip
root * /var/www/pjsmets.com/html
file_server
}
d. My complete Caddy config:
;
; Ansible managed
;
; source: https://github.com/mholt/caddy/blob/master/dist/init/linux-systemd/caddy.service
; version: 6be0386
; changes: Set variables via Ansible
[Unit]
Description=Caddy HTTP/2 web server
Documentation=https://caddyserver.com/docs
After=network-online.target
Wants=network-online.target systemd-networkd-wait-online.service
StartLimitIntervalSec=86400
StartLimitBurst=5
[Service]
Restart=on-failure
; User and group the process will run as.
User=www-data
Group=www-data
; Letsencrypt-issued certificates will be written to this directory.
Environment=CADDYPATH=/etc/ssl/caddy
ExecStart="/usr/local/bin/caddy" run --environ --config "/etc/caddy/Caddyfile"
ExecReload="/usr/local/bin/caddy" reload --config "/etc/caddy/Caddyfile"
; Limit the number of file descriptors; see `man systemd.exec` for more limit settings.
LimitNOFILE=1048576
; Use private /tmp and /var/tmp, which are discarded after caddy stops.
PrivateTmp=true
; Use a minimal /dev
PrivateDevices=true
; Hide /home, /root, and /run/user. Nobody will steal your SSH-keys.
ProtectHome=false
; Make /usr, /boot, /etc and possibly some more folders read-only.
ProtectSystem=full
; … except /etc/ssl/caddy, because we want Letsencrypt-certificates there.
; This merely retains r/w access rights, it does not add any new. Must still be writable on the host!
ReadWriteDirectories=/etc/ssl/caddy /var/log/caddy
; The following additional security directives only work with systemd v229 or later.
; They further retrict privileges that can be gained by caddy.
; Note that you may have to add capabilities required by any plugins in use.
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
AmbientCapabilities=CAP_NET_BIND_SERVICE
NoNewPrivileges=true
[Install]
WantedBy=multi-user.target
3. The problem I’m having:
I’m playing around with monitoring my Caddy setup and I’m wondering how to monitor the “golden signals”:
- Latency/response time
- Traffic
- Errors
For the response times, the Caddy docs already give some nice sample queries. For the other 2, it’s not so clear to me how to measure them.
- Traffic: the
caddy_http_requests_totalmetric gives counts per middleware handler. How can this be converted into total incoming traffic on the server? The docs warn about just summing everything up:Because all middleware handlers are instrumented, and many requests are handled by multiple handlers, make sure not to simply sum all the counters together.
- Errors: There is
caddy_http_request_errors_total, but this seems to combine 400 and 500 errors. Its it somehow possible to split this up?
4. Error messages and/or full log output:
/
5. What I already tried:
6. Links to relevant resources:
See inline links.
)
