When should a new problem be opened in Dynatrace?

A new problem should be opened in Dynatrace when service requests are impacted. This is crucial because service requests are directly tied to the performance and availability of applications and services that users depend on. When there is an issue affecting service requests, it not only affects the functionality of an application but can also lead to user dissatisfaction and potential financial loss for a business. Identifying and addressing these problems promptly is essential for maintaining a good user experience and ensuring that services run smoothly.

Opening a problem when service requests are impacted enables teams to investigate and resolve issues efficiently, leveraging Dynatrace's capabilities to pinpoint the root cause of performance bottlenecks, errors, or other anomalies. This proactive approach helps in ensuring that the overall health of the application or service is maintained, minimizing downtime or degradation in user experience.

In contrast, waiting until usage analytics are complete, when all processes are functioning, or when user actions are insufficient does not directly address immediate issues affecting service delivery. These scenarios may provide insights or data that are useful for long-term strategies or improvements, but they do not provide the urgent response needed when service requests are already experiencing problems.