The product analytics you already have

Summary

Software engineers frequently rely on separate product analytics tools and teams to answer user behavior questions, creating disjointed data models and delayed insights. Existing debugging telemetry within tools like Sentry—specifically spans, structured logs, and application metrics—can serve as the primary source for product metrics. Developers enrich request spans with business-level attributes, record discrete business events through wide structured logs, and track KPIs with metric counters and distributions. This unified telemetry links business outcomes directly to underlying traces, errors, releases, and source code lines, enabling immediate root-cause analysis and automated alerts. While multi-session cohort and funnel aggregation remains a current tooling gap, standard telemetry solves day-to-day adoption, performance, and revenue questions.

Context

Product analytics and engineering telemetry are conventionally separated, causing delays where analytics dashboards detect adoption drops weeks later without explaining root technical causes.

Approach / What changed

Developers repurpose spans, structured logs, and application metrics by attaching business-level attributes such as user tiers and revenue deltas directly to existing application telemetry in Sentry.

Takeaways

• Telemetry spans with custom business attributes enable simultaneous querying of feature adoption, runtime performance, and error rates in a single interface.
• Structured logs capture discrete revenue and business events while remaining correlated to underlying traces, errors, and specific commit releases.
• Complex cross-session funnels and 30-day cohort retention analysis remain difficult to reconstruct purely from request-scoped spans and event logs without specialized aggregation layers.

Related reading

• Sentry · May 5, 2026

  Introducing Application Metrics: Track the signal, see the spike, jump to the trace

  Sentry launched Application Metrics to capture application signals without pre-aggregating counters or discarding high-cardinality attributes like user IDs, project IDs, and regions. The system supports counters, distributions, and gauges within the existing SDK while linking each metric event directly to trace IDs for integrated debugging. Engineers demonstrated the feature by troubleshooting a Session Replay failure that triggered silently when sessions exceeded 1,000 video segments. By instrumenting distributions for replay event counts with project and replay attributes, the team isolated seven affected occurrences, navigated to connected traces and log lines, and reproduced the issue. Application Metrics comes enabled in recent SDK versions with 5GB included per plan.

  Ben Coe

• Sentry · May 6, 2026

  Improved debugging for Expo apps with the React Native SDK