Monitor Supermetry

Check readiness, protect Prometheus metrics and inspect live data-health signals.

Monitor service readiness, Prometheus metrics, and ingestion health.

Check that the process is ready to serve requests.
Terminal window
```
curl -fsS http://127.0.0.1:8787/readyz
```
/healthz reports that the process is alive; /readyz returns 503 until the application is ready.
Generate a metrics token and add it to the environment file when Prometheus connects remotely.
Terminal window
```
openssl rand -hex 32
sudoedit /etc/supermetry/supermetry.env
```
```
SUPERMETRY_METRICS_TOKEN=PASTE_THE_GENERATED_VALUE
```
Restart Supermetry after saving the file.
Terminal window
```
sudo systemctl restart supermetry
```
Test the Prometheus endpoint with the same token.
Terminal window
```
curl -fsS -H 'Authorization: Bearer PASTE_THE_GENERATED_VALUE' \
  http://127.0.0.1:8787/metrics
```
Without a token, /metrics accepts only direct loopback requests without forwarding headers. Other requests receive 401 Unauthorized.
In the dashboard, open Data health. It shows intake rate, rejected events, queue depth, day-close lag, collection corrections, and dropped traffic.

What you should see: readiness returns {"status":"ok"}, metrics return Prometheus text, and Data health refreshes live signals.

Related