Dashboarding
Dynatrace dashboards, notebooks, and data explorer explained.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Data Explorer in new tenants?

AntonioSousa
DynaMight Guru
DynaMight Guru

I have a new tenant, but with no Data Explorer. Even the graphs in Unified Analysis View show the Data Explorer type, and even if I put 

  • /ui/apps/dynatrace.classic.data.explorer/ui/data-explorer

in the URL, it shows briefly Data Explorer (it really is there) but then the following appears:

dataexplorer.png

How are we supposed to explore data/metrics that aren't yet in Grail?

Antonio Sousa
7 REPLIES 7

zietho
Dynatrace Leader
Dynatrace Leader

Hey @AntonioSousa , 

for new tenants, we removed Data Explorer because its use cases should now be covered by the Dashboards and Notebooks app. 

To help us see what might still be missing for you: Which concrete data or metrics are you trying to explore that you feel you cannot access or analyze with Dashboards or Notebooks today?

regards

Thomas

@zietho ,

 

metrics.png

 

Antonio Sousa

Julius_Loman
DynaMight Legend
DynaMight Legend

@zietho I have a different use case, which I already raised a product idea for - https://community.dynatrace.com/t5/Product-ideas/Globally-run-DQL-in-modal-window-for-ad-hoc-query/i... 
Data Explorer was great and fast when exploring metrics. Notebooks are not. It takes a while to open a notebook , run write/run a query and see results. Often, I just need to grab the DQL or some data results (like event.provider or even.type from bizevents) and use it elsewhere. Notebooks are great for analysing data, but are bad for ad-hoc querying. Dashboards are even worse fit for that. Either I have dozens of "untitled" notebooks, or I have a long notebook with is slow to load (due to the data) and it's difficult to navigate in it.

Please introduce a modal DQL query - it seems the functionality is there already, just needs to be used.


@AntonioSousa from my experience the non-grail metrics (residing in cassandra btw) are:

  • billing metrics (replaced by dt.system.events table)
  • SLO functions metrics (SLO in Gen3 works differently)
  • RUM Classic metrics - there is a different set of metrics with New RUM experience
  • Kubernetes classic metrics

Rest is typically marginal and has a replacement, see more here, here or here.

Dynatrace Ambassador | Alanata a.s., Slovakia, Dynatrace Master Partner

dannemca
DynaMight Guru
DynaMight Guru

Beside Data Explorer, I noticed that we also "lost" the Settings Classic. I am not able to create alerting profiles and notification integration for a new client. I know we can do it using workflow, but the classic option is "costless".

Site Reliability Engineer @ Kyndryl

Most of the notifications can be already accomplished with simple workflows. Afaik the remaining gaps (delayed notifications for example) should be resolved with simple workflows within upcoming weeks.

Dynatrace Ambassador | Alanata a.s., Slovakia, Dynatrace Master Partner

I completely agree with your point. But I remember several years ago, during the transition to version 2, features were relocated but accompanied by clear guidance: 'Here is the new functionality, and this is how to use it.' Currently, it feels like elements are simply removed, leaving users to guess and figure out where the missing features are supposed to be. good luck finding where this went'. 

fuelled by coffee and curiosity.  searching for a job,

rgarzon1
Champion

To me , Data Explorer was deprecated because they realized its metrics didn't align with those generated using DQL in Notebooks. Ultimately, removing it was the most practical decision.

fuelled by coffee and curiosity.  searching for a job,

Featured Posts