In today’s fast-paced digital world, simply knowing that an application is running is not enough. What really matters is understanding how well it is performing from the inside. This is where Dynatrace Deep Monitoring plays a crucial role.
Deep Monitoring in Dynatrace gives you detailed visibility into your application at the code level. Instead of just checking whether a service is up or down, it helps you understand how each request is processed, where delays are happening, and what exactly is causing performance issues.
What is Deep Monitoring in Dynatrace, and its benefits
Deep Monitoring is a feature in Dynatrace that tracks application behaviour in real time by analysing individual transactions and code execution. It supports multiple technologies such as Java, .NET, Node.js, and more.
Once enabled, it automatically captures:
- Method-level execution details
- Service-to-service communication
- Database queries and response times
- Errors and exceptions in the code
This level of detail helps teams quickly identify bottlenecks and improve overall application performance.
Key Benefits of Deep Monitoring
1. Complete Code-Level Visibility: Deep Monitoring allows you to see exactly what is happening inside your application. You can trace every request from start to end and identify slow methods or failing services.
2. Faster Root Cause Analysis: Instead of spending hours debugging, Dynatrace automatically identifies the root cause of issues. This reduces downtime and improves team productivity.
3. End-to-End Transaction Tracing: You can track how a single user request moves across multiple services and systems. This is especially useful in microservices architectures.
4. Proactive Issue Detection: With continuous monitoring and AI analysis, issues can be detected before they impact end users.
5. Reduced Manual Effort: There is no need for complex configurations. Deep Monitoring works automatically once OneAgent is installed.
Step-by-Step Guide to Enable Deep Monitoring Manually in Dynatrace
Step 1: Deep Monitoring will be enabled automatically for critical processes, but sometimes it needs restarting of the process in the server, as shown in the snapshot.
Step 2: Sometimes you will see the status Not Enabled for Deep Monitoring for some critical processes, as shown in snapshot 2 below. Then follow Step 3 and change from default to Monitor for Deep monitoring by going to process settings, then you will see a restart required, as shown in Step 1
Step 3: If you see Not enabled status for Deep Monitoring for the critical process, then go to settings and change the status of Deep Monitoring to Monitor and check the status of Deep Monitoring for the Process as shown in the below Snapshot below.
Once you have completed step 3, you will restart the required status in Deep Monitoring for the process, as shown in Step 1 Snapshot.
Step 4: Log in to the server and restart the process to enable Deep Monitoring in Dynatrace. Before proceeding with the restart, ensure that the process name and its path in Dynatrace match exactly with the details available on the server, as shown in the screenshots below.
Path in Server: Since this is a Windows Server, copy the EXE path of the process and verify that the same path is correctly reflected in Dynatrace
Once you have validated the Name and EXE path of the Process, restart the process/service in the Service (Windows: Press Windows + R, type services.msc, and press Enter. In the Services window, locate the required process, right-click on it, and select Restart.)
Once the process is restarted, you will see the Deep Monitoring status as enabled, as shown in the screenshot below.
Process Overview Page
When Should You Use Deep Monitoring
Deep Monitoring is highly useful in the following situations:
- When applications are facing performance issues and require detailed analysis
- In complex environments like microservices or cloud-based systems
- When you need to monitor critical business transactions
- During production, troubleshooting and performance tuning
