Metrics: connect Prometheus or an OpenTelemetry service in words #46

Merged
jcoffey-dev merged 1 commits from feature/metrics-connect into main 2026-09-28 22:02:08 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev bdbefd831d Metrics: connect Prometheus or an OpenTelemetry service in words
ci / build (pull_request) Successful in 1m39s
ci / publish (pull_request) Skipped
The metrics pages open with where the server's numbers go.

Prometheus: a switch, a user name and a password made in the browser
(shown once), then the scrape address (/metrics/prometheus on the
server's web address), a scrape job to paste into prometheus.yml, and a
check that the endpoint answers. Without a user name it warns that
anyone who can reach the server can read the numbers.

OpenTelemetry: Honeycomb (key and dataset as headers), Grafana Cloud
(OTLP endpoint, instance ID and token as Basic auth, with a note that
counters go out as deltas), or your own collector over HTTP or gRPC. An
HTTP endpoint in the settings is used exactly as given, so /v1/metrics
is added to a bare collector address. A saved Honeycomb key is kept when
the field is left empty; Grafana's token, which the server never sends
back, is asked for again when its settings change.

The page's own settings (which metrics) are folded underneath.
2026-09-28 14:55:55 -07:00