Dynatrace Reviews

We use the product on our applications for monitoring and troubleshooting errors through customized dashboards.

The major impact of improvement is from AppMon in our development area. Now we are enable to find applications problems more quickly.

The best feature of the product for me is the real troubleshooting capability through the PurePath analysis. 

I also like the Transaction Flow dashlet where I can see the real path of our web request through the application's layers.

I don't much like the Java Management Extension. I would rather do administration tasks in a web GUI.

Database monitoring and server performance. Apart from that, error handling and log tracking are also cool features.

There are multiple servers, so to track each server performance is very tough. Dynatrace really did an awesome job to provide us a better solution.

Server performance, because our company has multiple servers. To track each server manually without an application is very hectic. Dynatrace solves the problem by graph to monitor it all instantly.

Dashboards are too clumsy, so it is good to keep less on dashboards and be easier to find the sections. 

Dynatrace is bit costly and not easily affordable.

We use it to find database hotspots, method hotspots, CPU, JVM , Disk I/O and more.

Has helped us find issues such as application suspension and to improve web services data.

PurePath, Database Hotspots, Method Hotspots, CPU, JVM, disk I/O and other graphs.

Find the right method, give the cause of suspension, give tips for resolution, and one call query to find method.

We were using a freeware tool and we needed all the information in one tool.

Identifying and solving SQL queries that were affecting application performance.  Monitoring server and database performance.   

We had a client experience where a high number of simultaneous users were choking system performance which we were able to identify and fix.

The ability to real-time monitor servers and databases without any major drain on application resources is invaluable.  

No major request for additional features. 

Ability to better identify SDQ script errors would be helpful.

We use it to identify and trace bottleneck issues, pinpoint them, and fix them.

One example is that we were able to identify a SQL query which ran multiple times (redundancy) and fix the issue, improving the overall system.

In addition, we are able to look for errors in the logs so we know what is wrong with the system, and then get a developer to fix the issues.

There is also a lot of information, such as a user satisfaction index, to learn about the customer experience regarding page load times or errors encountered on different pages. This information is valuable for the design team.

Although there are many useful features in Dynatrace, I personally find PurePaths to be the most useful. This is the key element that I will use when trying to identify a problem.

I would like to see Dynatrace be more user-friendly. Sometimes there are too many options to choose from, which is good, but it can become confusing on how to proceed.

Our experience with Dynatrace is pretty good. We were using another monitoring software but Dynatrace has far more comprehensive and useful details to help us to identify bottleneck issues and fix them.

We use it to monitor customer user experience, performance issues, and unexpected errors. Dynatrace Appmon provides us with the ability to proactively identify issues within our systems which could be impacting our customers.

We have done several improvements to our single-page apps to improve initial load and response times. We have improved performance in areas that Dynatrace APM identifies as "Hot Spots". One of the big wins for us is that we were able to find root cause of a long known memory leak in our thick client applications. 

UEM is extremely valuable is it gives you performance measurements as close to the user as possible. The geographical view provides a nice visualization of performance on a map.

The web version of the client interface needs more features that are in the Java-based thick client. I barely use the web interface because I cannot get the level of detail that the thick client provides nor can I perform the bulk of the administration tasks I do on a regular basis.

• Server monitoring
• Performance monitoring
• Logging
• Profiling
• Alert triggering
• Network monitoring
• Database monitoring

We setup triggers for certain critical events. When these events happen, alert notifications are sent to the support team to take immediate action.

The alert trigger. This frees up our IT team. Also, they will be the first one to notice any interruption in the services and take action to recover the services. 

I hope going forward it can provide more functionalities for application profiling. I also hope it can provide more logging view, collecting, and search functions.

Website performance monitoring of load times for both desktop and mobile web.

Comparison of our site performance to other financial services companies to ensure we balance the delivery of rich content, which enhances the user experience, with comparable page load times to ensure it's not at the cost of performance. 

We seek to understand the areas of page composition that have the greatest impact on load time performance so we can focus our efforts on optimization to improve the user experience.

Understanding what elements on the page contribute to load time and the primary areas to focus on for improvement.

The daily metrics which help us analyze the page composition and the corresponding performance metrics so we can quickly and easily determine when something has changed, to aid in root cause analysis.

Perhaps there is a FAQ which explains the metrics and how to interpret them, and I just haven't seen it. This would be beneficial in providing context to allow sharing the daily metrics reported within the company.