Metrics (Trace Connected) in Open 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

Get started with sending metrics from JavaScript or Python projects with these docs: https://docs.sentry.io/product/explore/metrics/getting-started/

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 - 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

[mohitpatel-ghl]

Any default metrics that you’d like Sentry to send automatically
@Dhrumil-Sentry

We want to track the heap memory consumption, sometimes on users side page is becomes unresponsive or crashes due to excessing memory consumption.
We already have the logic on our code which computes memory at every certain interval, i'm just thinking if this metric feature could be a good approach to log it to sentry & then analyze it over there. Any suggestions over here in respect to metrics feautre

[Dhrumil-Sentry]

@mohitpatel-ghl Given you already have the logic to compute this - you can add this as a distribution metric so that you can track the p50,p90 of memory consumption across users. Def a good use case for metrics

[mohitpatel-ghl]

And @Dhrumil-Sentry does this metrics feature depends on any sampling like trace sampling rate or any other. Because sometimes we observed that all data is not being logged on dashboard

[Dhrumil-Sentry]

@mohitpatel-ghl the trace sample rate only applies to spans and not to these metrics. There can be a few mins of delay in us ingesting metrics and making them available to query. You can also go to the Stats page in the Org settings and select Metrics and confirm nothing was dropped on our server side.

If you still think any data is being dropped - Can you please open an issue here: https://github.com/getsentry/sentry-javascript/issues - we'd need a few more details from you to be able to debug

[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!

[Dhrumil-Sentry]

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

[KyGuy2002]

Thank you! Does this not work with the cloudflare sdk yet? Im not seeing the method on "@sentry/cloudflare": "^10.23.0" but I do see it on "@sentry/react": "^10.23.0"

[Dhrumil-Sentry]

@KyGuy2002 - thanks for the catch - We need to export these changes from the Cloudflare side - We'll do this very soon

[KyGuy2002]

Ok sounds good. Thanks for the response.

[lirigithub]

Hello, we would like to try the beta. Slug is dealzone. Thanks!

[Dhrumil-Sentry]

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

Let us know if you have any feedback or face any troubles

[EandrewJones]

Perfect timing for this feature! We would love to try: homa-ej.

[Dhrumil-Sentry]

@EandrewJones Your org should have access now - Please find the JS/Python instructions here:

https://docs.sentry.io/platforms/javascript/guides/nextjs/metrics/
https://docs.sentry.io/platforms/python/metrics/

Let us know if you have any trouble getting started !

[idobenamram]

we would love to try the beta! slug is nexus-ai-0s. Thanks!!

[Dhrumil-Sentry]

@idobenamram Your org should has access- Please find the JS/Python instructions here:

https://docs.sentry.io/platforms/javascript/guides/nextjs/metrics/
https://docs.sentry.io/platforms/python/metrics/

Would love to hear any feedback about the UX/SDK experience once you try this 🙏

[mjlescano]

nice! could we try out the beta at foil? 🙏 (using the Node.js lib)

[Dhrumil-Sentry]

@mjlescano Your org should has access- Please find the JS/Python instructions here:

https://docs.sentry.io/platforms/javascript/guides/nextjs/metrics/
https://docs.sentry.io/platforms/python/metrics/

Let us know if you hit any snags

[olena-gurushots]

Would love to try it out! The org is datascenes. Thank you!

[Dhrumil-Sentry]

@olena-gurushots Your org should has access- Please find the JS/Python instructions here:

https://docs.sentry.io/platforms/javascript/guides/nextjs/metrics/
https://docs.sentry.io/platforms/python/metrics/

Let us know if you hit face any troubles

[boris-w]

I really need this, my Organization Slug is teable

[Dhrumil-Sentry]

@boris-w Your org should has access- Please find the JS/Python instructions here:

https://docs.sentry.io/platforms/javascript/guides/nextjs/metrics/
https://docs.sentry.io/platforms/python/metrics/

Any feedback is appreciated

[ClemannD]

Requesting access for https://clemann-developments.sentry.io please

[Dhrumil-Sentry]

@ClemannD You should have access. Please see these docs to get started: https://docs.sentry.io/platforms/javascript/guides/nextjs/metrics/

Let us know if you hit any snags

[gaurav-peswani-truva]

We really want to try this out. Can we please get access for the organization truva?

[gaurav-peswani-truva]

Also are the metric examples mentioned in the description the only supported values or we can send any key as desired? We are planning to use this for sending Prisma metrics mentioned at https://www.prisma.io/docs/orm/prisma-client/observability-and-logging/metrics.

[Dhrumil-Sentry]

@gaurav-peswani-truva You should have access. Please see these docs to get started: https://docs.sentry.io/platforms/javascript/guides/nextjs/metrics/

You can send any counter/gauge/distribution type metric using the Sentry SDK - the examples I mentioned are only representative

Let us know if you hit any snags

[asyd]

Hello there! Is there a way to test this feature in a self-hosted deployment?

Cheers

[Dhrumil-Sentry]

We generally publish self hosted support once the feature is generally available which is likely to happen by end of April

[thomaseizinger]

Are there any updates around the Rust SDK? getsentry/sentry-rust#938 doesn't mention anything and there also doesn't seem to be any activity on the PRs.

[Dhrumil-Sentry]

We're not actively working on Rust right now - it's one of our very lesser used SDKs so we're waiting on some more community feedback asking for it for prioritization

[thomaseizinger]

Okay thank you! Please take this as a request for prioritization then. We are very happy with Sentry for monitoring our customer-deployed apps and would love to gather metrics around how they perform via the same platform.

[cjtheham]

Are there any updates on when Metric Alerts will be available?

[Dhrumil-Sentry]

@cjtheham Very soon - We should have support rolling out in the next 2-3 weeks 🙏 Thanks for your patience

[patrickdundas]

@Dhrumil-Sentry - team is anxiously waiting for this. I see Metrics Alert Config documented here now, but not available in my account yet. Does my account need to be opted-in to this alert option (we are already in the Metrics Beta)

[zackkitzmiller]

z19r and hexagon-tickets please? This is basically exactly what we're looking for right now in both orgs.

[bcoe]

@zackkitzmiller you should have access to Explore > Metrics. Let us know if that's not the case, or you bump into any problems?

[Syed-RI]

Usage quota and billing? Are they still TBD? What are we thinking of? Size ? Number? Event? 🤔

[alexjillard]

@Syed-RI We're still working through the specifics, so no concrete details to share yet. We'll get pricing details out as soon as we can, though.

[carlos-musetti]

Hi! We would love to test this at firmstudio

[alexjillard]

Hey @carlos-musetti, you should have access now. Take a look at the getting started docs, and please send us any feedback you've got!

[martinbean]

Hi. I’m a little unsure on how “counters” work.

Say I create a counter with the name test-counter. Day 1, I send a count of 5. Day 2, I send a count of 7. Will these counts be summed, or will the new count (7) replace the old count (5)?

[The-LukeZ]

.gauge ist for "setting" the value and .count is for adding X to an already existing count (starts as 0).

[martinbean]

So I’ve just emitted my first gauge, but it seems Sentry wants to group it by either second or minute, or aggregate it using a function like min, max, or avg.

Is there no way I can just emit a value and say, “This metric’s value was X at this date and time?” Basically, I want to record counts of records (e.g. users) so I can see how that count’s gone up or down over time; not aggregate it or group it.

[drxcheng]

Can you enable for "thoughtexchange" please? Thank you!

[alexjillard]

@drxcheng I sent you an email regarding onboarding your org in the beta

[drxcheng]

Thank @alexjillard ! Can you send to xu.cheng@thoughtexchange.com so I can forward to our IT team please?

[TeTiRoss]

hey, when this feature is expected to be rolled out, along with alerts?
we are looking into using Sentry and Metrics is the main thing that we would need.

[alexjillard]

@TeTiRoss Alerts are in progress, and will ship to the orgs in Beta very soon. We're currently planning on a full GA of Metrics late April/early May.

[AbhiPrasad]

The metric size limit is actually a bit annoying in practice. It prevents me from attaching useful stuff like db query plans or a db query itself to the metric (which the high cardinality nature of sentry metrics should allow me to do easily - I can add it to logs!). I can easily attach this info when I use sentry errors, tracing, or logs, so it feels weird when I can't do it with metrics.

Right now I have to do something like so:

/**
 * This sends both a monitoring metric and a debug log for the duration of a data query.
 * - The metric enables dashboards and alerts regarding query performance.
 * - The debug log provides deeper context (like query plans and arguments) for investigating 
 * latency. Attaching large metadata directly to metrics often triggers size limit 
 * constraints (e.g., 2 KiB limits).
 */
function recordQueryDuration(
  args: QueryArgs,
  queryDurationMs: number,
  response: Response | undefined = undefined,
) {
  const attributes: Record<string, unknown> = {
    "url.full": window.location.href,
    "query.is_slow": queryDurationMs > 10000,
    page: "query_explorer",
  };

  // Extract internal trace IDs from headers if present
  const traceId = response?.headers?.get("x-provider-internal-trace-id");
  if (traceId) {
    attributes["provider.trace_id"] = traceId;
  }

  Sentry.metrics.distribution("analytics.query_duration_ms", queryDurationMs, {
    unit: "millisecond",
    attributes,
  });

  const logAttributes: Record<string, unknown> = {
    ...attributes,
    "analytics.query_duration_ms": queryDurationMs,
  };

  // Add redacted query arguments to the log context
  for (const [key, value] of Object.entries(redactQueryArgs(args))) {
    logAttributes[`query.args.${key}`] = value;
  }

  // Extract and attach the execution plan if available
  const queryPlan = response?.headers?.get("x-provider-query-plan");
  if (queryPlan) {
    logAttributes["query.plan"] = extractPlan(response);
  }

  Sentry.logger.debug("Data Provider Query", logAttributes);
}

I know logs just give me the metric, but I want the nice UX. I guess the alternative would be to add numeric attributes from logs to the metrics views (but then I would want unit support!).

[bcoe]

@AbhiPrasad the issue is, if we're charging per-event for metrics, we need to ensure that they hit a price point that's palatable. If we lift the size limit, it becomes an issue for per event pricing.

How would you feel about paying for byte volume rather than event count?

[AbhiPrasad]

I think byte volume is reasonable, but then why metrics over logs? What I'm probably running into is just the greater problem of metrics and logs having such big overlap. It's not easy to know when to use what if metrics don't have the size limit constraints it has today.

[pranav100000]

hello, I'd like to try this. slug is
aether-a2
thank you!
@Dhrumil-Sentry @alexjillard

[bcoe]

Hello @pranav100000, your account is on a plan that should have access to metrics already. You'll see it listed under "Explore" in the Sentry UI.

[fabhari]

Hi,

Am planning to plot custom charts with my own sveltekit dashboard.
is there a way to extract metrics data from my self-hosted sentry ?
@Dhrumil-Sentry @alexjillard

Thanks
Hari

[alexjillard]

Hi @fabhari, there's nothing built to directly extract metrics from self-hosted or SaaS right now. With self-hosted you should be able to build something alongside Sentry to query the data directly and extract anything you need.

[loganprice537-hub]

I think there a way

…

On Mon, Mar 16, 2026, 10:39 AM Hari ***@***.***> wrote: Hi all, Am planning to plot custom charts with my own sveltekit dashboard. is there a way to extract metrics data from my self-hosted sentry ? Thanks Hari — Reply to this email directly, view it on GitHub <#102275 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B7VALJGLS4EJPGZEDEYWEAL4Q7KV3AVCNFSM6AAAAACKPXAN3WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMJVGY4TAMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[jackson-lewis]

Hey, we've just started using Metrics and looking to pull the data out via the REST API. While Metrics are not listed in the docs, it is known by the API when I set the dataset to "metrics".

However, when playing around with various params, I just can't seem to get the data out. Stuck on this 400 response.

{
  "detail": "Need at least one function"
}

This is my request: https://sentry.io/api/0/organizations/<org>/events/?project=<project>&statsPeriod=24h&environment=dev&dataset=metrics

Any help around getting the correctly formatted request would be super helpful. The most important is to get the value, and some custom attributes I've setup.

[loganprice537-hub]

Ok, I'll take a look.

…

On Mon, Mar 16, 2026, 8:47 AM Jackson Lewis ***@***.***> wrote: Hey, we've just started using Metrics and looking to pull the data out via the REST API. While Metrics are not listed in the docs <https://docs.sentry.io/api/explore/query-explore-events-in-table-format/#:~:text=REQUIRED-,choices,-%3A>, it is known bu the API when I set the dataset to "metrics". However, when playing around with various params, I just can't seem to get the data out. Stuck on this 400 response. { "detail": "Need at least one function" } This is my request: https://sentry.io/api/0/organizations/ <org>/events/?project=<project>&statsPeriod=24h&environment=dev&dataset=metrics Any help around getting the correctly formatted request would be super helpful. The most important is to get the value, and some custom attributes I've setup. — Reply to this email directly, view it on GitHub <#102275 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B7VALJH7IVFYBXF3BNYRLJL4Q7ZXXAVCNFSM6AAAAACKPXAN3WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMJVHEYTAMI> . You are receiving this because you commented.Message ID: ***@***.***>