Error Tracking

One of your users hits an error, and the app shows something like “Oops, something went wrong. We’re looking into it.” But what happens next? How do you get notified about the error? How do you understand what went wrong?

An Error Tracker is the missing link. It collects errors from your application and sends them to a central system, so you’re notified and can see what went wrong. It tells you where to look, and what to fix. Without it, you’re guessing.

Let Bugsink help you stay proactive and in control, so you can focus on what you do best: creating new errors features!

Key Features

Bugsink is designed to help you identify and resolve errors fast. It offers:

• Alerts: Immediate notifications when issues arise, allowing for prompt attention and resolution.

• Grouping into Issues: Automatic clustering of similar errors into issues, helping you distinguish between a single issue that happens often and multiple distinct problems.

• Comprehensive Stacktraces: Comprehensive stack traces accompanied by local variable values, offering deep insights into the state of your application during an error.

Alerts

Bugsink alerts you when something breaks — no need to wait for a user report. Alerts cover:

• New issues: Something broke for the first time.
• Regressions: An issue that you thought you fixed is back.
• Unmuted issues: You silenced an alert until some time in the future, and now it’s that time.

Alerts help you catch problems early, before users start emailing or leaving bad reviews. They turn invisible errors into visible tasks: you don’t need to tail logs or grep through files to know something went wrong.

If a new bug slips into production, you’ll hear about it the moment it happens, often before anyone reports it. And because error events are grouped into issues, you get one clear alert per problem, not a flood of noise.

→ Learn more about Alerts.

Grouping into Issues

Seeing the same error repeated hundreds of times doesn’t help. Bugsink groups related errors automatically, turning a flood of events into a manageable list of problems to fix:

• One cause, one issue: Similar errors are grouped based on key attributes like type, message, and context.
• Less noise: Instead of hundreds of events, you get a single issue to investigate.

Whether it’s an exception or a log message, Bugsink looks at what matters — the structure, content, and origin — to group things that belong together. The defaults work well for most projects, but you can fine-tune them if needed.

→ Learn more about Grouping.

Comprehensive Stacktraces

When an error happens, you want details – right away, and without fluff. A good stacktrace gives you that: full context, no guesswork. Nothing hidden behind tabs, no digging required. It’s how you go from “something broke” to understanding what and why.

Here’s what that looks like:

Some key principles:

• Simple & clean: The stacktrace is shown at the top of the page, so it’s the first thing you see. The format is clear, highlighting what matters. In-app frames and library frames are separated to help you focus.

• Complete: No information is hidden by default. You get the full picture up front—no need to click around or expand hidden sections.

• Local variables: You see the values that variables actually held at the time of the error. This makes it easier to understand the context and spot the problem.

Stacktraces are the core of debugging. They show you exactly where the error occurred and how your code got there. With that information, you can jump straight into fixing it – no guessing, no noise.

That’s why in Bugsink the stacktrace isn’t just part of the page – it is the page. So you can do what you came to do: figure out the problem and fix it.

Next up: read about our focus on self-hosting.