sentry-instrumentation-guide

To choose the right telemetry signal for instrumentation, use a decision framework that evaluates whether an event should be an error, trace, log, or metric, ensuring useful data and avoiding miscategorization across your service.

Emit a metric instead of a log when you need to track aggregate numerical values over time, whereas logs capture discrete events; applying a telemetry decision framework resolves these overlaps and retention considerations.

Review existing instrumentation for coverage gaps by applying a signal decision framework to check consistency across services, ensuring every event is correctly categorized as an error, span, log, or metric.

Yes, you can guide coding agents by providing a clear rule for what telemetry signal to emit, delegating the specific wiring of errors, traces, logs, or metrics to the corresponding SDK skills.

Yes, the instrumentation decision framework explicitly aligns with Sentry SDK guidance to determine the correct signal, resolving overlaps between errors, spans, span attributes, logs, and metrics.