If you are able to query the data and get that result in Grail then you could use the Davis anomaly detector to do just that (until it is possibly added in any future product), I use it for BizEvents on Grail where we see an abnormal amount of failed order pushes information being received.
I can confirm that this is the way to go on the new platform:
1. Create a custom anomaly detection (query via DQL + maketimeseries command if itâs not a built-in or custom timeseries)
2. Create a workflow listening to the anomaly events to notify or create a ticket
In terms of data points, any measurements available on Grail can be used for that. For RUM, e.g. page load timings of specific pages or views (based on page/view summary events), request durations of specific requests, specific error types etc. Currently, there is no categorization of performance in terms of Adpex available.
For classic, we also offer key user actions to possible cover your use case already today @9sagarelluru .
I am looking to enable RUM on Grail on a few servers in an application with 20 servers total.
I donât see a way to enable just 2 of the 20 production servers to ease into using this on production.
Is that something that will be available, or is there someway that I am not seeing?
Can you explain why you want to do it that way?
Youâre right that this is something thatâs not possible. You can only disable/enable RUM overall for e.g. a specific process group. But itâs not possible to enable/disable only the RUM on Grail piece / config. Also this is not planned on our end.
HI @paul_kapeller How can one request access to the preview?
We are going into a âpublicâ preview soon and I will then update this post - for now you can reach out to your account contact (e.g. Customer Success Manager, Insights AnalystâŚ) to inquire for participation, which will then be managed in a couple of weeks.
Request form for preview participation:
Thanks, already did.
Thanks @paul_kapeller for organized and insightful content.
Hi Paul, we have requested for preview participation a couple of weeks ago. Can we somewhere check if access has been activated? Thanks
Currently, we can see the image size in the waterfall analysis. Would it be possible to make this information available in Grail as well? It would be very helpful for identifying images that could be resized within the application.
On Grail, we are currently capturing encoded and decoded body size, transfer size of requests captured.
Since we recently published the semantic dictionary for user events, you can review the full request model here
Or are you referring to something else?
@GregOReilly have you signed up for the Preview program ?
If you are not in the preview, you wonât see any data in the user.sessions table. If you are part of the preview, you need to configure your apps, see https://docs.dynatrace.com/docs/shortlink/rum-on-grail-capture-data
General availability is planned later this year.
Eagerly waiting for extending the 35 day retention time. When will it happen?
Can you elaborate why / what data youâd like to store for longer and why?
As it stands now, we will launch a preview program for extended retention ~at the time we go GA with the new RUM experience. Mid next calendar year we are planning for the GA of extended retention in Digital Experience.
Quite simply, GA does it, and the client (Iâm a partner) wants to use Dynatrace for UX. But canât if limited to 35 daysâŚ
Since the new RUM experience data resides in Grail, why is this not available with its launch along with processing rules?
I had several cases with customers with RUM classic offering where longer retention (60 days or more) would solve the case. 35 days is simply just one month. Many customers have monthly releases and comparing the data with the previous month is essential. With custom metrics, itâs solvable only to some degree.
Hi,
Is there a way to get something like Apdex with the new RUM? Customers are familiar with this easy-to-understand indicator.
Hello @paul_kapeller,
Is there a way to change how the page.name value is detected?
Iâm looking for something equivalent to the User Action Naming Rules, which allowed fairly advanced matching using regex.
My first attempts with DQL feel cumbersome and hard to reproduce consistently across dashboard widgets:
fetch user.events, samplingRatio: 1, scanLimitGBytes: 500
| filter characteristics.has_page_summary == true OR characteristics.has_w3c_navigation_timings == true
| filter dt.rum.application.entity == âAPPLICATION-8C7D0B9CE4FDFC30â
| filter isNotNull(page.name)
| fieldsAdd error.count = error.csp_violation_count + error.exception_count + error.http_4xx_count + error.http_5xx_count
| filter matchesValue( page.name, â/products/*â)
| fieldsAdd variabilized = replacePattern( page.url.path, ââ/âLONGâ/ââ, â/xxx/â)
| parse variabilized, âââDATA:shorturl â\/xxx\/â âââ
| fieldsAdd target = concat(shorturl, â/xxx/â)
| fieldsKeep page.url.path, page.name, target
The parameterization of URL paths seems to be the foundation for correctly aggregating Core Web Vitals statistics.
Thank you for your help.
Regards

