Data Enrichment

By now, you should have events flowing into your project(s). This guide will cover essential topics such as data enrichment, filtering unwanted events, and issue grouping. If you get stuck anywhere, please Ask Sentry AI or join our Discord community.

Step 1: Enriching Your Event Data

Adding Custom Context

There are several ways you can enrich your data in Sentry. Adding tags, custom contexts, and breadcrumbs will help organize, filter, and analyze errors more effectively. See this quick walkthrough on adding a tag:

Step 2: Ensure Your Traces Are Instrumented Properly

Verify That Sentry's Tracing Auto-Instrumentation is Set Up Optimally

Once Tracing is turned on, Sentry will auto-instrument your spans. If any additional instrumentation is needed, look into your platform's instrumentation documentation for additional options.

Custom Instrumentation For Any Additional Performance Metrics

For any gaps in Sentry's auto-instrumentation, you can use custom instrumentation to collect additional spans and span metrics. This enables you to focus your instrumentation on critical areas of your application to optimize you configuration. For example, if you have an e-commerce app, you may want to track pageloads and checkout errors to pinpoint issues by provider, region, or app version.

The video below is an example of what's possible with custom instrumentation:

Step 3: Filtering Unwanted events

Filtering out events that are not actionable or expected during normal operations is essential for maintaining a clean and relevant issue tracking system. Issue and trace filtering are project-specific and can be accomplished within the SDK or the server via inbound filters:

Step 4: Grouping Your issues

If you are noticing individual errors that should be grouped together, you can customize your issue grouping algorithm. Additional grouping customization can be accomplished via issue merging or Sentry's custom grouping.