Gen3 Problems UI – Root Cause Analysis and Problem Investigation Compared to Problem Classic

sagarhb — Wed, 08 Jul 2026 10:05:09 GMT

Hi Team,

We have recently started using the Gen3 Problems UI and have observed several usability challenges compared to the Problem Classic (Gen2) interface. These challenges are impacting our day-to-day monitoring and incident troubleshooting.

1. Root Cause Analysis

In the Gen3 UI, when a problem alert is generated, identifying the root cause requires multiple navigation steps and additional analysis.

In the Problem Classic (Gen2) UI, the root cause could be identified within a few clicks, enabling much faster incident triage and troubleshooting.

Is there a recommended workflow or configuration in Gen3 that provides a similar root cause investigation experience?

2. Problem Details and Infrastructure Visibility

In the Gen3 Problems UI, it is difficult to quickly identify:

Impacted server(s)
Impacted service(s)
Service dependencies
Overall infrastructure context

In Problem Classic, this information was readily available from the problem view, making it much easier to understand the issue and start troubleshooting.

Is there an equivalent view in Gen3 that provides the same level of visibility, or is this planned as part of future enhancements?

Our operations team relies on fast root cause analysis during production incidents, and currently we find the Problem Classic (Gen2) experience much more intuitive and efficient than the Gen3 UI.

We would appreciate any recommendations, best practices, or information on upcoming enhancements that can help improve the investigation experience in Gen3.

topic Gen3 Problems UI – Root Cause Analysis and Problem Investigation Compared to Problem Classic in Alerting

Gen3 Problems UI – Root Cause Analysis and Problem Investigation Compared to Problem Classic

1. Root Cause Analysis

2. Problem Details and Infrastructure Visibility