topic Re: Loss of details when investigating failures in Open Q&A

Loss of details when investigating failures

DavidFT — Mon, 10 Aug 2026 13:47:52 GMT

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.

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.

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

Re: Loss of details when investigating failures

Julius_Loman — Mon, 10 Aug 2026 20:42:06 GMT

@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.

Re: Loss of details when investigating failures

julian_farias — Tue, 11 Aug 2026 00:11:58 GMT

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).

Re: Loss of details when investigating failures

julian_farias — Tue, 11 Aug 2026 00:14:58 GMT

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

Re: Loss of details when investigating failures

DavidFT — Tue, 11 Aug 2026 07:45:11 GMT

Yes, same service !

Re: Loss of details when investigating failures

DavidFT — Tue, 11 Aug 2026 07:49:46 GMT

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

Grail