# Application Metrics — Trace-Connected and High-Cardinality > Sentry's application metrics are trace-connected and high-cardinality. Tag any measurement with customer_id, route, or region — and drill from any spike into the trace and code behind it. **URL:** https://sentry.io/product/metrics/ --- Track the signals that matter, slice by any attribute at query time, and jump straight to the trace when something spikes — without getting penalized for adding context. ## Features ### Every metric, linked to the trace it came from A spike isn't a number on a graph — it's a clickable path to the exact request, span, and line of code. Drill from a p95 outlier into the slow span that produced it Jump from a counter increment to the issue and stack trace behind it Correlate metric movements with releases, feature flags, and deploys automatically ### Instrument once. Ask anything. Tag every measurement with the dimensions you actually debug with — customer_id, route, region, plan, build SHA. High cardinality is the default, not a limit. Emit raw measurements, then ask new questions later — without redeploying. Counters, gauges, and distributions — first-class, with the tags you need Slice and group after the fact — like grouping checkout.failed by customer_id Filter with structured queries like route:"/checkout" AND region:"eu-west" Alert on any structured dimension, not just pre-canned rollups ### Get the answer from your metrics Calculate error rates and conversion ratios from the metrics you already emit. Aggregate by sum, avg, count, or p50/p95/p99 Combine up to 26 queries with equations like A / B for ratios, or (A + (B / 2)) / C for Apdex Use derived series in dashboards and alerts ## Features - **Equations**: Combine metrics with arithmetic to derive the number you actually care about — ratios, deltas, and composite scores like Apdex. Reference up to 26 metric queries (A, B, C…) in a single equation: A / B for a failure ratio, A - B against a baseline, or (A + (B / 2)) / C for a satisfaction score. — [Learn more](https://docs.sentry.io/product/metrics/#multiple-metrics-and-equations) - **Metric-Based Alerts**: Alert on any structured dimension. Route to the on-call who owns that surface. - **Metric Dashboards**: Compose error rates, latency, and throughput next to the issues and traces they describe. - **Trace-connected**: Traditional metrics tools tell you if something changed. Trace-connected metrics tell you why. Metrics are automatically tagged with trace_id and span_id — so when checkout.failed spikes, you click into an exemplar and land in the exact trace, spans, logs, and errors that produced it. Debugging stops being speculation. — [Learn more](https://docs.sentry.io/platforms/javascript/metrics/#trace-context) - **Metric aggregation**: View related metrics — error rates, latency, throughput — alongside the issues and traces they describe for one-pane root-cause analysis. ## FAQ **How much do application metrics cost?** All Sentry plans come with 5 GB. Additional usage beyond that costs $0.50/GB. Usage will be applied to your pay-as-you-go budget. **Why metrics in Sentry?** Traditional metrics tools punish you for the tags you actually need and live in a different tab from your errors and [traces](https://sentry.io/product/tracing/). Sentry treats high cardinality as the default for application-level signals, and links every emission to the trace and issue behind it. The result: you go from a metric spike to the trace, span, and stack frame that caused it — without leaving Sentry. **Can I send my OTel metrics?** Not today — and it's a deliberate choice. OTLP metrics are pre-aggregated before they reach us, which strips out the high-cardinality detail that makes our query model useful. If you need OTel-style infra metrics, pair Sentry with your existing metrics backend. **How to get started?** If you already have the Sentry SDK installed, you're a few lines away from emitting metrics. Call `Sentry.metrics.count()`, `Sentry.metrics.gauge()`, or `Sentry.metrics.distribution()` directly from your code — no separate import, no extra service to wire up. Release, environment, and SDK context are attached automatically. Check out our docs to [read more.](https://docs.sentry.io/product/metrics/getting-started/) ## Of course we have more metrics content - [How to get started with metrics](https://www.youtube.com/watch?v=lDDj6ohKMoY): A walkthrough of getting started with application metrics in Sentry. - [Why we killed our metrics product and rebuilt it](https://blog.sentry.io/the-metrics-product-we-built-worked-but-we-killed-it-and-started-over-anyway/): Two years ago, Sentry built a metrics product that worked great on paper. But when we dogfooded it, we realized it was not what our customers really needed. - [Application Metrics caught my broken size estimator](https://blog.sentry.io/metrics-caught-ai-size-estimate/): Some numbers are too important to bury in a log or lose to sampling. A video converter became the clearest case for tracking KPIs with Application Metrics. ## Testimonials > With Metrics, we can have a more central location for all our error tracking and data analysis. > I was able to get our first metrics in Sentry very quickly! --- *Source: [sentry.io/product/metrics/](https://sentry.io/product/metrics/)*