Connect Uptime Kuma to Saasmetry

What Saasmetry reads

• monitors:read
• heartbeats:read

Refreshed every 5 min. Read-only throughout: Saasmetry never writes to Uptime Kuma.

Create the credential

Uptime Kuma is self-hosted, so the credential is created in your own instance rather than on a vendor dashboard.

1. Uptime Kuma → Profile → Settings → API Keys → Add API Key.
2. Give Saasmetry the key and your instance URL.

Uptime Kuma documentation

Worth knowing

• The key opens exactly one endpoint, /metrics — that is the only route Uptime Kuma protects with it, and it lists every monitor on the instance with its current state. Nothing has to be made public.
• Uptime percentages and outage history exist only through a published status page on 1.x. Add its slug in Saasmetry if you want them. 2.x publishes uptime over /metrics and needs no status page at all.
• 1.x publishes no monitor IDs over /metrics, so Saasmetry identifies monitors by name there. Both a name and a numeric ID are accepted as a product's identifier.

Is it safe to paste?

Use read-only scopes wherever the provider offers them. Saasmetry encrypts the credential and only reads provider data.

Also worth connecting

• Better Stack
• GlitchTip