Hello Antonio,
sorry to hear that the update was not precepted well - the Exception analysis, along with the Top web requests and Top database statements have been consolidated that the look and feel and capabilities of the different specialized analysis tools are the same.
The exception analysis is now much more powerful as it now also allows to define custom splittings, to store and share your existing analysis views and also to easily create metrics out of it.
Filtering by messages is still available when going to the “Exception details” via the menu next to a service or exception class.
The overhaul of the specific help pages is currently ongoing and they should be available soon. We will improve here to synchronize this better in the future.
Can you give me more insights which specific functionality are you missing in the new perspective?
Hi @Thomas R. It's nice to have the MDA splittings, but does not help if we want to filter on a specific exception:
In the above example, I don't have a filter applied. Even with specific filters applied, the exception list is still truncated, making it difficult to find a specific exception that may not occur frequently.
This is a huge step back in functionality.
Hi @Thomas R. I agree with Michael. The MDA is quite advanced but we need something much more simple: search for the exception and analyze it. That's it. If you provide use advanced analysis dimension but without a fast and efficient way to search the exceptions it is a mess. The big limit of the MDA, as Michael explained, is that the data is truncated. Most often we get exceptions not very frequent that have a HUGE impact on our environments. If we truncate it by the most frequent ones, we loose visibility into the critical issues. More, we cannot anymore filter by a substring contained in the exception class. It was possible on the old view:
Hope it helps you understand the issue here and for now I will keep using the old one hoping you will not remove that
Featured Posts
