Error Tracking Overview

Tindra captures unhandled exceptions, logged errors, and manually captured events from your applications.

What's in each event#

• Exception type and message: what went wrong
• Stacktrace: file, line, and surrounding code context
• Breadcrumbs: a timeline of activity leading up to the error
• User context: ID, email, username (if set by your SDK)
• Request context: URL, method, headers, body
• Environment: release version, environment tag, server name

Issues vs. events#

Tindra groups similar errors into issues. Two exceptions with the same type and stacktrace fingerprint land in the same issue.

• Issue: the unique problem (e.g., TypeError: Cannot read property 'id' of null)
• Event: a single occurrence of that problem

Events are searchable immediately after ingest. There is no async processing queue.

Issue lifecycle#

An issue opens when a new fingerprint is seen for the first time. Resolve it manually when the fix ships. If the same error reappears after the next release, the issue re-opens automatically.

Filtering#

Filter the issues list by environment, release, assigned user, or free-text search. Use the environment selector at the top of the dashboard to scope all views to a specific environment.

Next steps#

• Issues: searching, triaging, and resolving
• Environments: separate production from staging
• Releases: track which deploy introduced an error
• Alerts: get notified when error rates spike