analytics-instrumentation

To instrument Sentry spans accurately, apply the repository's trace wrapper to your code to ensure consistent tagging and cross-process propagation for performance tracing.

Registering MetaMetrics events requires completing governance reviews, performing enum checks, and validating event names before shipping to ensure telemetry instrumentation accuracy and compliance.

Estimate telemetry volume by analyzing production data through Sentry traces and dashboards, which informs capacity planning by providing actual usage metrics for your instrumentation.

Yes, updating Segment tracking requires following governance steps including enum checks and proper event registration before merging, ensuring consistent telemetry instrumentation across the codebase.

The best way to maintain consistent telemetry is to use trace wrappers for Sentry spans and complete governance reviews with enum checks for MetaMetrics and Segment events before shipping feature work.

You need a trace wrapper for Sentry instrumentation during feature work or performance tracing when cross-process propagation and consistent tagging across the codebase are required.