Connect Sentry or GlitchTip

Sentry and GlitchTip both speak the same Sentry SDK protocol. The Elido side is the same configuration for either — the only difference is the DSN you paste in.

This guide covers two directions: piping Elido alerts into your error tracker (so abuse / TLS / API problems show up as issues you can triage), and using Elido alongside your existing Sentry setup if you're already self-hosting GlitchTip.

Why connect them#

Elido emits operational events that are useful as Sentry issues:

• abuse.flagged — our scanner marked a destination URL as malware / phishing.
• domain.tls_renewed (failure variant) — Caddy could not renew a TLS cert.
• webhook.delivery_failed — your own webhook endpoint stopped responding.
• link.clicked.aggregated (anomaly variant) — sudden 10× traffic spike on a single link.

You probably don't want all of them as issues — pick the ones that need a human response.

Add the integration#

1. Dashboard → Integrations → Sentry / GlitchTip.
2. Paste your Sentry DSN. GlitchTip DSNs use the same format and work in the same field.
3. Pick the event kinds to forward. Default is just abuse.flagged and TLS renewal failures.
4. Click Send test event. You should see a "test issue" in your Sentry project within 10 seconds.
5. Save.

The integration runs server-side. We don't load the Sentry browser SDK in your dashboard — your DSN never reaches the visitor's browser.

What the issue looks like#

Each forwarded event becomes a Sentry-formatted issue with:

• event_id = Elido event id (so you can de-dupe).
• level = error for abuse + TLS failures, warning for webhook delivery failures, info for spike anomalies.
• fingerprint = workspace ID + event kind + relevant resource ID, so re-fires of the same issue group cleanly in Sentry.
• extra = full Elido event payload.
• tags = workspace, event_kind, plus the resource-specific tag (link_slug, domain, etc.).

GlitchTip notes#

GlitchTip implements the Sentry event ingestion API but not the full Sentry feature set. The integration only sends events through the ingestion endpoint, so any feature in that scope (issue grouping, fingerprints, search, alerting) works in GlitchTip too. Performance traces, replays, and profiling don't, but Elido doesn't send those anyway.

If you're self-hosting GlitchTip behind a private network, give Elido's egress IPs HTTP access. The full list is on our trust page; the short version is 5.75.0.0/16 (Hetzner FRA) and 51.79.0.0/16 (OVH SGP).

Disable#

Click Disconnect in the integration page. The DSN is wiped, and no further events are sent. Your existing Sentry issues are not deleted — they stay in your Sentry project.

Limits#

• 1 Sentry destination per workspace. If you need to fan out to multiple Sentry projects, use webhooks and a small proxy.
• We respect Sentry's 50/s default rate limit per project. Spike anomalies are sampled before send to stay under the limit.

Troubleshooting#

Test event arrives but real events don't. Check that you've selected the right event kinds in the integration settings. The default selection is conservative.

Events arrive but tags are empty. Sentry sometimes truncates tag values longer than 200 chars (slugs, domains) — they end up as unknown. This is a Sentry limit, not ours.

GlitchTip ingest endpoint rejects with 429. Your GlitchTip instance is rate-limiting. Either raise the per-project limit in GlitchTip's admin, or filter the event kinds down to the ones you need.

DSN was rotated and now we get 401s. Update the DSN in the integration page. There's no auto-detect for DSN rotation.