topic Re: Real-time (or near-real-time) alternative to closed-session carrier field for web RUM? in Real User Monitoring

Real-time (or near-real-time) alternative to closed-session carrier field for web RUM?

julsgs — Mon, 21 Sep 2026 20:08:48 GMT

We're monitoring mobile connections for an ISP client using a web application (RUM Classic) and today we rely on a custom USQL metric (uscm.*) that uses the built-in "carrier" field as a dimension. This works, but it only reflects data once the user session is closed, which for our use case (near real-time visibility of connections per carrier) is too delayed.

What we've confirmed so far from the docs and community:

USQL (and any custom metric built on top of it) only processes closed sessions - a Dynatrace staff member confirmed in an older thread there are no plans to support live sessions here.
"carrier" is a built-in field, populated server-side from the source IP against a network-operator database - it's not something our app's JavaScript computes or could send early.
Business events (sendBizEvent/sendEvent) are sent detached from the session and are close to real-time, but per the Business event enrichment docs, they only get automatic geolocation enrichment (continent/country/region/city) from the client IP - not carrier or ISP.

Our question: is there any supported way to get "carrier" (or an equivalent mobile-operator field) attached to data closer to real time, without waiting for the full session to close? Specifically:

Does the new RUM experience (powered by Grail) expose carrier/isp at the individual user-action or event level, with lower latency than waiting for the full session to close?
Is there any way to have business events automatically enriched with carrier/isp the same way they get geolocation, or is this a hard limitation today?
If not, is a custom server-side IP-to-carrier lookup (maintained by us) the only realistic path to get this in near real time?

Any pointers from the Dynatrace team or others who've solved something similar would be great. Thanks!

Re: Real-time (or near-real-time) alternative to closed-session carrier field for web RUM?

sujit_k_singh — Tue, 22 Sep 2026 03:49:19 GMT

Hi @julsgs

1: Does the new RUM (Grail) expose carrier/ISP at the user action/event level with lower latency?

The new Grail-backed RUM stores data in two tables: user.events and user.sessions
The carrier attribute is part of the RUM semantic model and is associated with session context. However, I have not found definitive documentation confirming whether this field is populated directly within user.events, or only becomes available when the corresponding session record is written to user.sessions.

the most practical next step is to validate directly in your environment, run below dql

fetch user.events
| filter isNotNull(carrier)
| fields timestamp, carrier, useraction.name
| limit 20

If recent event records contain the carrier field, then Grail may provide the near real-time visibility you're looking for without waiting for session closure based on that you can create metrics.

2: Is there any way to have business events automatically enriched with carrier/isp the same way they get geolocation, or is this a hard limitation today?

No — this is a hard limitation today.

3: If not, is a custom server-side IP-to-carrier lookup (maintained by us) the only realistic path to get this in near real time?

If carrier information is not available in user.events, the available options appear to be:

Validate carrier availability in user.events first
Enrich Business Events via OpenPipeline
Perform a server-side IP-to-carrier lookup
Continue using the existing USQL-based metric

My recommendation would be to first verify whether the carrier attribute is available in user.events. If it is, that likely provides the simplest and most native near real-time solution.

If not, then OpenPipeline enrichment or a server-side IP-to-carrier lookup currently appear to be the most realistic approaches for obtaining carrier-level visibility without waiting for session closure.

Thanks,

Sujit

Re: Real-time (or near-real-time) alternative to closed-session carrier field for web RUM?

julsgs — Tue, 22 Sep 2026 17:27:23 GMT

Hi Sujit, thanks for the detailed answer.

I ran the query you suggested, and user.events came back completely empty for our application - even without the carrier filter. That tells us our environment is still on RUM Classic and hasn't adopted the new RUM experience yet, so we couldn't actually validate whether carrier is available at the event level there.

One more detail on our side: this is a classic-licensed environment, no DPS.

Given that, is there anything else you'd suggest we look at?

Thanks again for the help.