Connect GlitchTip to Saasmetry

What Saasmetry reads

• issues:read
• events:read
• projects:read
• monitors:read

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

Create the credential

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

1. Your GlitchTip → Profile → Auth tokens → Create token.
2. Grant the scopes below.
3. Give Saasmetry the instance URL and your organization slug as well.

GlitchTip documentation

Exactly what to grant

• project:read
• event:read
• org:read

Worth knowing

• GlitchTip implements Sentry's API, so Saasmetry talks to it exactly as it talks to Sentry — but only the endpoints GlitchTip has actually implemented.
• The issue filter takes a project's numeric ID. A slug is rejected outright with a 422, so pick the project from the list rather than typing the name from the URL.
• GlitchTip's uptime monitors are picked up automatically — no extra configuration. A monitor is matched to a product by the project it is attached to, or failing that by the domain it probes, so a monitor on https://acme.com lands on the product whose domain is acme.com.
• A new monitor reports no uptime percentage until it has ten checks. Below that the ratio is a rounding artefact rather than an availability figure, and it would be printed beside Uptime Kuma's full-day number.

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

• Sentry
• Better Stack
• Uptime Kuma