Use Sentry only for features GlitchTip lacks

Cost

Source available. The server is under FSL, not an open source licence. The hosted service has a free tier and paid plans.

How to do it

Sentry has grouped errors since 2010 and ships a server release each month, the latest 26.10.0 on 16 October 2026. Its SDKs are under MIT and are the same ones GlitchTip reads, so moving means changing the DSN. The server is under FSL-1.1-Apache-2.0 since November 2023, which is not an OSI licence. Each server version turns into Apache-2.0 two years after release. Self-hosting Sentry needs 4 cores and 16 GB of RAM, so most teams who pick it pay for the hosted service. Send browser errors to it too, as Collect script errors from visitors' browsers says.

Examples

Using these examples: they show one way to follow this rule. Keep the behaviour and the check, not the syntax. Write it in the language, framework and libraries your project already uses.

JavaScript example

import * as Sentry from '@sentry/node';

Sentry.init({ dsn: process.env.SENTRY_DSN, release: process.env.RELEASE, sendDefaultPii: false });

Python example

import os
import sentry_sdk

sentry_sdk.init(dsn=os.environ["SENTRY_DSN"], release=os.environ["RELEASE"], send_default_pii=False)

How to check

A decision record names the Sentry feature GlitchTip lacks. A test error thrown in production shows up in Sentry within 60 seconds, with the release tag.

Sources

• Sentry licensing
• Self-hosted Sentry

Related rules

• Collect script errors from visitors' browsers in Website