Dynatrace Reviews

Appmon:

• Drill downs to root causes.
• Easy to find the performance bottlenecks.
• Full insight into all classes.
• UEM helps to identify user experience and detailed steps performed by the user.

I have identified and fixed the following performance issues in non-production before we release the app:

• Identified memory leaks that caused heap utilization maxed out.
• Identified thread bottlenecks at JVM.
• Identified JDBC connection pool limits.

There are so many!

• Transaction flow: Helps to identify server health at every layer.
• Threads on JVM: Helps to identify active, hung, and count.
• GC: Helps to identify GC collection time and number of times GC kicks in.
• UEM: Helps to identify user experience.

DT Saas: Does not have all the features that Appmon has. Maybe in the future releases it may have all features.

Application performance monitoring for testing our pre-production environments. Along with that, we use AppMon to create B/T's for alerting and graphing trends.

Prior to the use of Appmon, our team was in the dark. We had zero visibility into our production application, and it would take up to days to find out why our clients were being impacted and how.

Since Appmon has been leveraged, we are now down to just hours (sometimes minutes) in resolution times.

PurePath analytics, I can't imagine not having this feature in your application. Not only have we been able to improve troubleshooting, but we have also used PurePath data (response times) to improve and tune application performance.

Ease of Use. I find it is very difficult to train someone in using this application. As amazing as it can be, the learning curve is extensive.

Java-based microservices (couple of dozen) monitoring and their dependencies (Oracle, MySQL, RabbitMQ, and Elasticsearch). Apart from monitoring (with alerts), I use the Dynatrace solution to investigate reported issues by clients.

It eases the investigation process (faster feedback loop with clients), better pro-activity on possible outages (in order to avoid outages), and eases the process of fine tuning allocation of resources to processes.

• Dashboards: Most critical information on a single view and in a very-customizable way.
• Alerts: Stays on top of probable issues.
• Services monitoring: Helps fine tune resource allocation (CPU and memory).

I would like to have more visibility into Python processes. Meanwhile, we are thinking about "fronting" our Python processes with a fully supported web server, such as Nginx.

1. Application performance monitoring root cause analysis 
2. User experience analysis 
3. Proactive monitoring (application, third-party API, and availability and host)

It helps to identify the problem in a minute and user experience metrics provide valuable data to the business team to understand how the application performs at the end user level. Overall, it is an amazing tool for application root cause analysis and business function analytics.

• The microservices container topology view
• It supports Kubernetes and cloud monitoring platforms.

Its needs to focus more on open source areas, like Apache umbrella products and availability motioning areas.

SaaS infrastructure monitoring and alerting. We use it to monitor over a 1000 servers in AWS.

It is our main SaaS monitoring and alerting solution, and it allows us to identify many problems that we would miss if we did not have a comprehensive monitoring solution.

• Automatic alerting on system problems
• Failure rate increases
• Latency increases, etc. 

This stuff all works out-of-the-box, and is essential for a DevOps team to be aware of to identify production issues.

• The Web UI can be slow and hard to understand. 
• The integration with PagerDuty is currently broken on mobile. 
• It often produces "false alarms" and cannot identify failure patterns over days/weeks that do not indicate concern.

Application performance diagnostics of our enterprise critical applications. Proactive monitoring of response times and trends. Performance and load testing of new versions.

• Helps us to quickly find performance issues with new applications or new feature introductions.
• Allows us to see response time, failure rate, user experience, and visualize trends.
• Root cause analysis of problems with live systems.
• Performance and load testing evaluations.

The ability to go from a high level performance view to a specific transaction. Dynatrace covers the important tiers and allows us to quickly find trends and root causes in all our critical application lifecycle steps (Ops, Dev, and Performance).

It is not clear which path the product will follow with Dynatrace in the cloud (or on-premise) and Appmon. As an existing customer who has invested heavily in training and using the Appmon version, it is not clear what are our long-term strategy should be to upgrade (Appmon vs Dynatrace).

User performance monitoring; to be able to proactively understand the user experience on our site.

• Ability to identify which pages are slow and cause frustration for our users.
• Ability to identify user browsers, user geographical location.
• Email alert and mobile app alert are very useful for informing the team that something is going wrong.

User Sessions. I am able to tell what the user experience is like on the web pages.

Also, I'm able to drill down to identify problem issues.

I would like the ability to export a user session into csv format. (I am aware that I can export a user session via a webhook).

We started using Dynatrace software as a better alerting and application monitoring mechanism. We are happy with the server monitoring, but we feel like the application monitoring should be improved.

I would definitely say it improved the functionality. We are able to prevent the major downtimes by proactive monitoring alerts.

• Server monitoring
• Dashboards
• PurePath

PurePath comparisons are the most useful feature.

It can be improved in narrowing the exact exception/ERROR in application monitoring. It should focus more on app monitoring and capture for some of the known alerts and be able to identify which system is having the issue.