Dynatrace Reviews

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.

The primary use case of the Dynatrace is to monitor our application and its performance.

It helps in many ways in our organization:

• managing capacity planning
• managing services performance
• tuning database performance and optimizing queries.

There are so many features which we find very useful. One of them is to use PurePath to pick out frustrated users, see where the issue is, and analyze why it is happening. Dynatrace helps a lot in find the issue and fixing it.

We are still exploring features. But one feature which would be great in the next release would be that it provide a summary of the main fail point for frustrated users, instead of our having to go to PurePath and look for it. It should provide the list of pain point areas in report format.

APM.

Real-time information allows us to proactively tackle an issue before it affects our clients.

The dashboard gives us a great overview.

The cost is somewhat high.

External monitoring of customer-facing web presence. We also use Appmon and DC RUM to monitor the physical and database status within the company as a whole.

Improves the ability to isolate issues and determine root cause with the same tool. This has helped us determine the scope of an outage event and better determine an ETR.

Knowing when systems performance is affected. This has helped to isolate infrastructure pain points.

Addition of support for security tokens for login automated testing. At the moment, I am unable to use Synthetic to automate user login. I believe the addition of local agents will address this need, but I have not had that verified.

We use Dynatrace for application health monitoring and investigation into any reported problem.

Dynatrace has helped us reduce the investigation time and troubleshooting time for any application issue.

Dynatrace PurePath and exception lists are used most of the time, but it is also a very good tool for application reporting.

It's a great tool for building dashboards related to application performance.

Improvements in Synthetic monitoring would be great. Certain features of thick client, if available in the web interface, would also be a great improvement.