Automatic anomaly detection and root cause identification minimizes alert spam
Dynatrace automates anomaly detection and root cause identification to minimize alert spam. When problems are detected, alerts are pushed to your chosen incident management and collaboration tool, like ServiceNow, Teams, and Slack. Here, the Dynatrace AI, Davis, has detected a problem and sent a Slack alert. 24/7 proactive monitoring and alerting gives you more time to focus on moving the needle forward.
Click on the green box to view problem
Free Trial
Free Trial
Book a Demo
Book a Demo
Welcome to Dynatrace!
This interactive product tour explores a backend service incident. Since Dynatrace automates business impact and root cause analysis, you can quickly triage, respond, and understand the impact.
View Tour Introduction
Problem
The problem card highlights the precise root cause and business impact to end users and applications. This information enables you to quickly triage and respond to the problem. In this case, Davis analyzed over 3 billion dependencies in real-time to identify the root cause as an issue in the CheckDestination service. Pinpointing the exact problem keeps you from endless data analysis and unnecessary war rooms, so you can meet SLAs.
Free Trial
Free Trial
Immediately understand the problem’s impact on applications, services, infrastructure, and real users.
Identify all impacted users and visually replay how users experience the problem.
Davis automatically identifies the root cause. Here we see the problem is an issue with the CheckDestination service, caused by a deployment change.
Davis, Dynatrace’s AI, continuously analyzes billions of dependencies to provide precise root cause.
The visual resolution path shows you the portion of your environment affected by the problem, from applications through infrastructure.
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
The visual resolution path shows you the portion of your environment affected by the problem, from applications through infrastructure.
The visual resolution path shows you the portion of your environment affected by the problem, from applications through infrastructure.
The visual resolution path shows you the portion of your environment affected by the problem, from applications through infrastructure.
Interactive legend
Next step
Hover over for info
Click to see popup
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
Click to expand
View page description
Analyze response time degradation
Book a Demo
Book a Demo
Analyze response time degradation
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
Analyze response time degradation
Analyze response time degradation
Analyze response time degradation
Analyze response time degradation
Analyze response time degradation
Analyze response time degradation
Analyze response time degradation
Analyze response time degradation
1 / 8
Next step
Hover over for info
Click to see popup
Click to expand
Business impact and root cause analyses enable you to quickly triage and respond to the problem
Immediately understand the problem from the user’s perspective
View page description
Session Replay
Visually replaying the session from the user's point of view provides understandable and indisputable video evidence of the exact issue with the user’s experience. It's easy to see how and when the user suffered the response time degradation. This visibility helps teams immediately understand what the end user is experiencing so you can prioritize the issue.
Under Distribution, you can see how much time is contributed by calls to other services, calls to databases, and code-level execution. Under Top findings, you can see the biggest hotspots.
View method hotspots
Response Time Analysis
The average response time observed during the problem timeframe is shown distributed across calls to other services, calls to databases, and code-level execution, with the biggest hotspots highlighted. Here, an anomaly in code execution time is the key contributor to the degraded CheckDestination response time. Quickly identifying the origination of performance bottlenecks enables targeted action to not only address current issues quickly, but also identify improvements that will have the greatest impact.
Free Trial
Free Trial
Interactive legend
Book a Demo
Book a Demo
Problem
896
View method hotspots
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
Problem
896
CheckDestination
CheckDestination
Details
Details
Problem
896
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
Problem
896
2 / 8
Next step
Hover over for info
Click to see popup
Click to expand
Quickly identify the origination of performance bottlenecks
View page description
896
Problem
View method hotspots
Method Hotspots
Method hotspots checks all the classes and methods that were executed to run the service under the call tree, and provides the exact method call contributing to the issue. In this case the method LocationParser.parseSectionIndex was identified as responsible for the problem. This automatic observability shows Dev precisely where to look in the codebase and saves hours manually reading thousands of lines of code to understand what needs to be fixed.
Free Trial
Free Trial
Interactive legend
Book a Demo
Book a Demo
View method hotspots
The LocationParser.parseSectionIndex method is the cause of the issue. This precise code-level information enables Dev teams to quickly resolve the issue. Now let's explore the impact on other services and verify this root cause.
CheckDestination
Details
CheckDestination
Details
Problem
896
Next step
Hover over for info
Click to see popup
Click to expand
3 / 8
Pinpoint precisely where to look in the codebase to resolve the issue
View page description
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
896
Problem
Analyze backtrace
Service Details
The service page shows which applications or services use the service and if the service makes any calls to other services or databases. Problem-specific service summaries quickly highlight the impact to the service and beyond. During this problem timeframe we see that service requests suffered response time and CPU consumption spikes. Tracing how these spikes propagate upstream from this backend service is critical to understanding the business impact.
Free Trial
Free Trial
Interactive legend
Book a Demo
Book a Demo
As previously identified by Davis, a deployment occurred directly prior to the problem.
CheckDestination
Details
CheckDestination
Problem
896
Problem
896
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
Details
Problem
896
Next step
Hover over for info
Click to see popup
Click to expand
4 / 8
Understand the problem impact to the service and beyond
Analyze backtrace
View page description
View method hotspots
Backtrace
A backtrace shows the sequence of upstream services that result in a request. In this case, we can see that multiple frontend services call CheckDestination, clearly highlighting service impacts of the problem. When troubleshooting or planning changes to a particular service, it is crucial to understand the upstream call chain to continuously ensure application and experience quality.
Free Trial
Free Trial
Interactive legend
Book a Demo
Book a Demo
View method hotspots
The easyTravel Customer Frontend service is an originator of the call chain. Let’s explore the problem impact on this frontend service.
CheckDestination
Details
Details
CheckDestination
Problem
896
Problem
896
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
CheckDestination
Details
CheckDestination
Details
Next step
Hover over for info
Click to see popup
Click to expand
5 / 8
Trace the call back upstream to identify the impact to application frontends
View page description
The response time degradation is clearly linked back to the CheckDestination service. Resolving this issue will restore normality.
896
Problem
View PurePaths
Service Flow
Service flow maps the sequence of service calls that are triggered by any service request. Here we can trace the response time degradation through the services, all the way to the CheckDestination service. Beyond troubleshooting, understanding the relationships between services enables you to more effectively make migration or architecture decisions.
Free Trial
Free Trial
Interactive legend
Book a Demo
Book a Demo
Problem
896
View PurePaths
Details
Details
Problem
896
Details
View PurePaths
Problem
896
Details
View PurePaths
show more
Next step
Hover over for info
Click to see popup
Click to expand
6 / 8
Visualize how a frontend service request flows down to the problematic code
show less
View page description
Focusing in on a single call path provides concrete evidence that the issue is in CheckDestination. Let’s go back to the Problem to resolve the issue.
896
Problem
View method hotspots
PurePath
Dynatrace’s patented distributed trace, PurePath, brings together data from multiple sources across hybrid and multi-cloud environments to analyze transactions end-to-end across every tier of your application technology stack. As applications and microservices become more complex, understanding the relationship between calling/receiving services is key in order to find the source of a problem. And using OpenTelemetry as an additional data source, Dynatrace extends your coverage and turns telemetry data into actionable answers, faster than ever.
Free Trial
Free Trial
Interactive legend
Book a Demo
Book a Demo
Problem
896
View method hotspots
Next step
Hover over for info
Click to see popup
Click to expand
7 / 8
Analyze transactions end-to-end across every tier of your app’s technology stack
View page description
Sem fringilla ut morbi tincidunt interdum velit euismod. Sedre risus ultricies tristique nullaye aliquet, agittis eu volutpat.
View method hotspots
Problem Remediation
Dynatrace’s AI, Davis, enables auto-remediation by reliably identifying issues and the underlying root cause. In this case the incident was triggered by a new deployment containing a code issue in the CheckDestination service. Davis identified this and was able to automatically roll back to a prior deployment, remediating the issue before it had further impact. AI and automation empower you to overcome accelerating cloud scale and complexity.
Free Trial
Free Trial
Interactive legend
Book a Demo
Book a Demo
Problem
896
Next step
Hover over for info
Click to see popup
Click to expand
8 / 8
Precise root cause identification enables Dynatrace to trigger auto-remediation workflows
View page description
