Metrics (Trace Connected) in Beta

[Dhrumil-Sentry]

We’re introducing Metrics that let you send counters, gauges, and distributions from your code to track things like email.sent, checkout.failed, or queue.depth — and pivot directly into the related traces, logs, and errors when something looks off.

TraceConnectedMetrics.mp4

If you'd like access for JavaScript or Python please comment with your org slug below or drop us a note at feedback-metrics@sentry.io

Why we built this

Metrics in most tools stop at charts — they show that something changed, but not why. When a checkout.failed counter spikes, you’re forced to switch tools and manually line up logs or traces to find the cause.

With Sentry, every metric event carries a trace_id.

That means you can:

• click into a sample and see the exact trace that produced the metric,
• open the related spans, logs, and errors,
• understand why the metric moved — slow database query, failed API call, bad deploy, etc.

So instead of “metric alert → guesswork,” debugging becomes a single flow: Metric spike → open a sample → trace waterfall → root cause.

How the UX works

Aggregates tab shows trends and totals across any attributes (e.g. sum(metrics_value) grouped by email_type).

Samples tab shows individual metric events with direct links to their trace — so you can jump straight into the logs, spans, and errors that occurred at the same moment. Allowing you to drill into any spikes or dips in your metrics and find relevant errors,traces or logs to look at.

How to get started

If you'd like access please comment with your org slug below or drop us a note at feedback-metrics@sentry.io

Python

You need to be on a min version of 2.43.0 of our Python SDKs

import sentry_sdk
from sentry_sdk import metrics

sentry_sdk.init(
    dsn="___PUBLIC_DSN___",
    _experiments={
        "enable_metrics": True,
    },
)
metrics.count("checkout.failed", 1, attributes={"route": "/checkout", "tenant": "acme"})
metrics.gauge("queue.depth", 42, attributes={"queue": "emails"})
metrics.distribution("cart.amount_usd", 187.5, attributes={"currency": "USD", "tenant": "acme"})

More details: getsentry/sentry-python#5042

JavaScript

You need to be on a min version of 10.20.0 for our JavaScript SDKs

Sentry.init({
  dsn: '<your-dsn>',
  _experiments: { enableMetrics: true },
});

// Counter — increment a metric (defaults to +1)
Sentry.metrics.count('checkout.failed', 1, {
  attributes: {
    route: '/checkout',
    tenant: 'acme',
    provider: 'stripe',
  },
});

// Gauge — set a current value
Sentry.metrics.gauge('queue.depth', 42, {
  unit: 'items',
  attributes: {
    queue: 'emails',
    region: 'us-east-1',
  },
});

// Distribution — record numeric values to compute p95, avg, sum, etc.
Sentry.metrics.distribution('cart.amount_usd', 187.5, {
  unit: 'usd',
  attributes: {
    currency: 'USD',
    tenant: 'acme',
  },
});

Each metric event includes:

• name, kind, value, attributes
• trace_id, span_id → used to link with other telemetry
• optional unit, byte_size

More details: getsentry/sentry-javascript#18055

When (and why) to use Metrics

Metrics are best for application and code based health signals — numeric indicators of whether your application logic is behaving as expected.

You should reach for metrics when you want to quantify what your code is doing

Examples:

• email.sent / email.failed
• job.processed / job.retried
• checkout.started / checkout.failed
• payment.declined / refund.issued
• queue.depth / pool.in_use
• search.zero_results

Feedback

We’re working on shipping Alerts, Saved Queries and dashboard widget building support very soon

We’d love to hear your feedback about the following

• Are the SDK APIs easy enough to send your desired metrics ?
• Any feedback about the Metrics Explorer UX - What could make this a better experience for you ?
• Any default metrics that you’d like Sentry to send automatically

[mohitpatel-ghl]

@Dhrumil-Sentry We would like to try this out
This is our sentry org url https://gohighlevel.sentry.io/

[Dhrumil-Sentry]

@mohitpatel-ghl You should have access now - Please follow the SDK instructions linked above and let us know if you hit any problems !

[mohitpatel-ghl]

@Dhrumil-Sentry I was checking metrics dashboard ,its written that* We're working to bring
Metrics support to Vue. Stay updated by joining the discussion!*

So just need to confirm if this is supported in sentry/vue or not & if not
then when can we expect this to be supported.

[Dhrumil-Sentry]

@mohitpatel-ghl - That was a bug in the copy we're showing - It's supported for all JS platforms - please see the SDK instructions here: getsentry/sentry-javascript#18055

[eddie-at-stan]

stan-yz please! This came just in time.

[Dhrumil-Sentry]

@eddie-at-stan you should have access now -Would love to hear any feedback !

[TwoTau]

I'd love to try this! Our org slug is scorecard

[Dhrumil-Sentry]

@TwoTau You should have access now

Here's the JS: getsentry/sentry-javascript#18055 and Python: getsentry/sentry-python#5042 SDK instructions

Please let us know if you hit any friction

[pshomov]

Will you support high cardnality attribute values - user id, tenant id, etc.? What will you consider as a billable metric item?
Would love to try this 🤩 . Our org slug is spectaflow.

[Dhrumil-Sentry]

@pshomov We're using a high volume event store for this solution - So we can definitely support high cardinality values like user_id etc.

We don't know pricing details yet but there will be no charge to using these Metrics while we're on Open Beta for a few months atleast.

I will say that the solution is mean to help developers track metrics with high cardinality tags and we're more likely to restrict how many attributes you could attach vs causing a cost explosion due to high cardinality - But all of this is TBD and we'd appreciate any feedback

Your org has access now. Here's the JS: getsentry/sentry-javascript#18055 and Python: getsentry/sentry-python#5042 SDK instructions

Any feedback appreciated !

[matt-roberts-navi]

Exactly what we need right now! Great timing with the availability. navi-ventures as the slug

[Dhrumil-Sentry]

@matt-roberts-navi Your org has access now. Here's the JS: getsentry/sentry-javascript#18055 and Python: getsentry/sentry-python#5042 SDK instructions . Let us know what you think !

[leoht]

Hey, really excited to read this is available – we'd love to try this out.
Our Sentry org URL is https://oddboxhq.sentry.io – let me know if you need anything else!

[Dhrumil-Sentry]

@leoht Your org has access now. Here's the JS: getsentry/sentry-javascript#18055 and Python: getsentry/sentry-python#5042 SDK instructions. Let me know if you hit any snags

[leoht]

Great thanks! Will give it a try

[leoht]

@Dhrumil-Sentry Just tried to implement a few metrics (using the Python SDK), though it seems they're not showing up in the UI at all. I'm still only able to see the default landing page with the tutorial/demo, though I'm able to see the corresponding trace in the UI.

What's the best way to give feedback on this one? Happy to open an issue

[Dhrumil-Sentry]

@leoht Can you please leave a comment on the Python SDK discussion with an example of a metric you're sending with the SDK: getsentry/sentry-python#5042

We'd need the version of the SDK you're using as well 🙏 - Thanks a lot for sharing feedback

[KyGuy2002]

I would like to try with kylan-ph org slug. Thanks!