- last edited on by
GosiaMurawska
What is the value proposition for having DEM metrics on dashboard?
One of the main benefits of having digital experience data on Grail is that practitioners will have access to all the real user monitoring as well as synthetic data generated by their front-end applications. In addition, Grail also enables the saving of granular data such as those that do not trigger back-end requests, captured without sessions, or from apps that are temporarily offline to name a few. Furthermore, while this data can be queried with DQL not everybody is going to be familiar with writing the precise queries required. Also, while querying raw data can be especially useful there could be additional costs incurred. However, metrics, available at no additional cost, are available via dashboards and the core DEM apps to meet the needs of your use-cases.
Are dashboards with digital experience metrics being migrated over from the classic to the latest Dy...
As the data model for RUM data has changed on the latest Dynatrace, the raw data collected is different and none of the existing dashboards will be migrated over. The process of creating dashboards on the latest Dynatrace is quite easy as you simply select the metrics you want to display when creating a dashboard.
|
|
Is my organization eligible for dashboards on the latest Dynatrace?
The following conditions need to be met:
- SaaS only on DPS contract (if not on DPS, please contact your sales rep)
- Next gen agents [link to blog post]
Why can’t the same metrics be migrated over from classic to the latest Dynatrace?
In classic, customers use metrics in dashboards, SLOs as well as other places. The metrics captured on Grail are not always the same as their counterparts on classic. It should be noted that some metrics will go away and be replaced by similar ones to accommodate modern technology and applications. Furthermore, some metrics will be replaced by new ones (with the same name) that are calculated differently, so values will not be the same necessarily.
How would I know which metrics on classic maps to which ones on the latest Dynatrace?
When building the metrics dashboard on the latest Dynatrace, clicking on the information (i) icon will open hints and links to further documentation where you will have information on the classic metrics that the new metric is replacing.
Which use-cases would I be able to satisfy with these metrics?
- Monitor the application health - performance and availability - of applications as experienced by users to ensure continuity in our service. (through Core Web Vitals, availability, error rates, load times)
- Monitor internal-facing applications or any private endpoints that are not accessible from the public internet through synthetic metrics
- Understand how new features are adopted and learn how we can improve adoption. (partially)
- Discover and be alerted / notified about new errors or certain thresholds reached via Dashboards, workflow automations and notifications, problems etc.
- While not available at GA, in the long-term, leverage user (and account) metadata to analyze use cases with cohort analysis. Compare cohorts.
I have problem alerts generated based on metrics. How will those be migrated over?
Currently, there are no plans yet for moving alerting profiles. In addition, there is no possibility to create problem alerts and notifications on the latest Dynatrace for October 2024. However no existing alerting profiles will stop to function and problems and alerting will continue to work as before on the old data model even if enabling the capturing of the new data model.
What are the costs associated with querying and displaying RUM metrics on dashboards?
The built-in metrics provided from RUM data will not carry any costs when used on Dashboards, Notebooks and other out-of-the-box apps within Dynatrace.
Will there be a RUM 'explorer' to query RUM data in notebooks and dashboards without using DQL? Similar to how there is a logs and metric explorer.
There will not be a separate RUM explorer, but the RUM metrics can be selected through the Metric explorer and will be listed under the Frontend category.
Featured Posts
