Other Sentry SDKs
Every official Sentry SDK can report to Bugtail: Go, Ruby, .NET, Java, Rust, Elixir, Flutter, React Native and the rest. There is no Bugtail package to install. You give the SDK a Bugtail DSN, and nothing else in your code changes.
Point the SDK at Bugtail
Create a collector with the Sentry compatible protocol under Settings > Projects and collectors and copy its DSN. It has this shape:
https://<key>@ingest.bugtail.eu/<project-id>Set it wherever your SDK takes its DSN, usually an option called dsn or an environment variable called SENTRY_DSN. Coming from Sentry, this is the only change.
What Bugtail reads
| The SDK sends | You find it under |
|---|---|
| Errors and messages | Issues |
| Transactions and their spans | Performance |
| Sessions | Releases |
| Logs | Logs |
Everything else an SDK may send, such as attachments, session replays, profiles, cron check-ins, user feedback or Sentry's own metrics, is accepted and ignored. Nothing breaks, but it does not show up either. Send metrics with OpenTelemetry or over HTTP instead.
Logs have to be turned on in most SDKs, with an option usually called enableLogs or enable_logs.
Moving from Sentry
- Your sample rates, releases, environments, tags and fingerprints keep working as they are.
- Source maps uploaded to Sentry are not in Bugtail. Upload them again for each new release.
- Alert rules are set up again under Alerts.