Hi,
I have a question about the title of the Problem.
The document, Problem lifespan example, describes the following case.
- Dynatrace detects an infrastructure-level performance incident. A new problem is created for tracking purposes and a notification is sent out via the Dynatrace mobile app.
- After a few minutes, the infrastructure problem leads to the appearance of a performance degradation problem in one of the application's services.
- Additional service-level performance degradation problems begin to appear. So what began as an isolated infrastructure-only problem has grown into a series of service-level problems that each have their root cause in the original incident in the infrastructure layer.
- Eventually the service-level problems begin to affect the user experience of your customers who are interacting with your application via desktop or mobile browsers. At this point in the problem life span you have an application problem with one root cause in the infrastructure layer and additional root causes in the service layer.
- Because Dynatrace understands all the dependencies in your environment it correlates the performance degradation problem your customers are experiencing with the original performance problem in the infrastructure layer, thereby facilitating quick problem resolution.
https://www.dynatrace.com/support/help/monitor/problems/basic-concepts/problem-lifespan-illustrated/
At the #1, I guess that the name of Problem may be like "CPU saturation". Then the issue proceeds to #5, I guess that the name will change to like "User action duration degradation".
Could you tell me whether the title of the Problem changes over time? I'm planning to integrate the Problem of Dynatrace to other systems. I want to consider how to integrate the title to our system.
Thanks,
Noah Kobayashi
Featured Posts
