Introduction
Bugtail collects the errors, logs, traces and metrics of your applications and shows them in one place. It works with the tools you already have: the official Sentry SDKs, OpenTelemetry, or a plain HTTP request. Everything is hosted in the EU.
Already using Sentry? Point your SDK at a Bugtail DSN. Nothing else in your code has to change.
How it is organised
Organisation. Your company, identified by its domain. It has its own dashboard at https://<organisation>.bugtail.eu, its own team and its own storage. Everyone you invite works in the same organisation.
Project. One application or service, such as your web shop or your API. Issues get a short reference from their project, such as SHOP-14, and every screen can be filtered by project.
Collector. The way data reaches a project. Each collector has its own key, speaks one protocol (Sentry, OpenTelemetry or Bugtail's own HTTP format) and has its own settings for sampling, retention and filtering. A project can have several, for example one for the backend and one for the browser.
You manage all three under Settings > Projects and collectors. See Collectors and keys for what each setting does.
What it collects
| Data | What you see | How it is sent |
|---|---|---|
| Errors | Grouped into issues with a count, a status and the stack trace | Sentry SDKs, HTTP |
| Logs | A searchable, live log explorer | Sentry SDKs, OpenTelemetry, HTTP |
| Traces | Latency and throughput per operation, the slowest spans, and full traces for the requests worth opening | Sentry SDKs, OpenTelemetry |
| Metrics | Counters, gauges and histograms over time | OpenTelemetry, HTTP |
| Sessions | A crash-free rate per release | Sentry SDKs that track sessions |
Where to start
- Follow the Quickstart to create your organisation and send a first event.
- Pick the guide for your platform under Connect an application in the menu.
- Set up alerts, so the right people hear about new problems.