Monitoring
Server health, bearer-protected /metrics, and optional Sentry integration.
The server exposes a health endpoint, installs a Prometheus recorder, and can initialize Sentry. Metrics and Sentry configuration are available independently of connected Cloud state; database-aware health probing is enabled when connected persistence is configured. Hosted Rustume Cloud operates its observability stack; self-hosted operators configure their own destinations.
Health
GET /health returns ok in normal mode. When connected state is active, it also probes PostgreSQL
and reports failure if the database cannot be reached.
Version
GET /version reports which build is serving:
curl -s http://localhost:3000/version
{"version":"0.44.0","commit":"c515854","built_at":"2026-07-25T19:38:00Z"}
commit matches the short commit in the image’s sha-<commit> tag, so a deploy can be confirmed
without reading the OpenAPI document or the JavaScript bundles. Builds without that metadata (for
example a local cargo run) report null for commit and built_at.
Metrics
GET /metrics requires a configured token and an authorization header:
curl -H "Authorization: Bearer ${METRICS_TOKEN}" http://localhost:3000/metrics
Credentials are not accepted through a query parameter. Which metrics are retained and alerted on depends on deployment operations.
Sentry
Set SENTRY_DSN to enable optional Sentry Tower integration:
SENTRY_DSN=https://[email protected]/...
Operators are responsible for data-scrubbing and retention settings before sending production events to a third-party telemetry provider.