Open Q&A
If there's no good subforum for your question - ask it here!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Loss of details when investigating failures

DavidFT
Contributor

Hello Community,

It seems to me that failure analysis is still more effective on the Classic stack than on the Grail one. More specifically, the Classic Services app is able to pinpoint the real exception behind a failure whereas the Grail one cannot. Here is an example to illustrate this.

DavidFT_0-1786369306660.png

Here, Dynatrace helps me identify a specific exception. No need for me to find anything else, the answer is right here right in front of my eyes.

For the exact same problem on Grail app, I do not benefit from such insights.

DavidFT_1-1786369394663.png

DavidFT_2-1786369409324.png

Is there a way to find this kind of information else where? Is it lost forever or is there any hope left to have it on Grail app?

Thanks for your attention,

David

5 REPLIES 5

Julius_Loman
DynaMight Legend
DynaMight Legend

@DavidFT is this really the same service? In the Gen3 view, you have just the setStatus and no exceptions that are visible on the Gen2 screenshots.


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

Yes, same service !

julian_farias
Participant

Hi ! 
I think the right comparison would be using this feature in Problems v3, but basically, what Dynatrace does is take you to that Classic view you mentioned (which should work for you anyway, since that is precisely what you are looking for).

julian_farias_0-1786407102087.png

 



Observability enthusiast

It is exactly the same function as the "Analyze failure rate degradation" feature in Classic.
julian_farias_1-1786407204117.png

 

Observability enthusiast

Well that's basically the problem : if I click on "Analyse failures", I don't have the same level of details. Here is another example :

Classic

 

DavidFT_12-1786434556914.png

 

 

Grail

DavidFT_10-1786434519822.png

DavidFT_11-1786434542196.png

Featured Posts

Community freeze: read-only from October 22, 6:00 AM UTC, while we move to Discourse. Outage (~1h) on October 26 at 9:00 AM UTC. Learn more.