Dynatrace Reviews

We are using this to find and troubleshoot issues with our applications, whether there are application issues with IIS or Tomcat, database or network issues. We also use Dynatrace to chart errors and monitor server health (memory/CPU/disk).

As we have grown, we have increased our licenses to be able to use this across most of our products to help troubleshoot problems in production. We have also used Dynatrace in our performance testing environments to get ahead of issues before they make it into production.

The ability to take each individual request and dive in to inspect what methods and calls are being made is extremely helpful. We can tell which application is serving the error, where the errors and performance issues lie, whether those are on the application server, database server, network, etc.

I would like to see the Business Transactions made easier, so you can distinguish users and companies (this can get very hairy for a large multi-tenant application). 

We should be able to easily simplify both the charting and slicing-and-dicing of user metrics with cookies that contain customer/user information.

We have used Dynatrace since they were their own company (before Compuware bought Gomez and spun both off into the company now known as Dynatrace) and the earliest version that I remember was version 2. We first got Dynatrace as a fire-fighting tool when we were having issues with one of our products. It helped us solve those problems, and has helped many times since.

Dynatrace helps us monitor our critical applications' health (performance) and measure the quality of service delivered to our customers (SLA and satisfaction).

Thanks to Dynatrace, we are able to quickly spot which tiers are causing a slowdown in order to limit unavailability.

In anaysing trends, we can detect performance degradation and avoid incidents.

Dynatrace gives us a live view on our multi-tiers application. It brings light where we were blind.

• We have drastically reduced the delay taken by the diagnostic phase. As we identify the root cause very rapidly, we can now focus on the solution and communication.
• We have enhanced our dialog with our customers. By comparing their feelings with objective measures, we are able to optimize where the pain point are.

Dynatrace monitors transactions (application), but also gives technical information (JVM, OS).

The value comes from the correlation of this huge amount of data. Dynatrace's engine is powerful enough to filter, split, and graph and "give sense from raw data".

UEM (User Experience Management) is an optional feature that we acquired and use a lot. It provides indicators from the customer's browser, reflecting more precisely on what our internal users are experiencing.

• Even if the engine can manage a huge amount of data, requests take time to succeed.
• The heavy client is not really user-friendly and the concepts (while powerful) are unintuitive.
• Automated reports are ugly, but the latest releases improve the web interface: A smarter way to share dashboards and indicators.

We use Dynatrace as our APM solution across our portfolio of web sites/applications. We use UEM for a line-of-sight view of client transactions and the performance of the application for the user.

Dynatrace has allowed us to pinpoint quickly any pain points our clients experience with our applications and respond accordingly. I like how fast we can deep dive into the PurePath to locate where issues are occurring.

We experienced immediate results with Dynatrace. During the POC/evaluation of the product, we found the application was making thousands of database queries unnecessarily causing performance issues. With this information, the development team was able to re-architect the app and improve performance.

We enabled UEM for all of our applications. This allows us to see exactly what the client is experiencing. This has been an invaluable feature.

I would like to see more features from the desktop client included in the web client. The web client is user-friendly and convenient, but would be even better if we could do in it what can be done with the desktop client.

We are a smaller startup. We do not have the luxury of time or staff resources to spend on the major tasks of implementing traditional server host monitoring, application performance monitoring, or log ingestion. Dynatrace was an amazing find! 

An additional benefit that we did not even realize at first were the dashboards! Dashboards were not even on our radar when we purchased it. Now, we have a giant TV hung in the office that shows various application and network metrics from a custom Dynatrace dashboard. We love it.

No other provider gives us log ingestion, Kubernetes/Docker monitoring, and application monitoring for NodeJS. Some competitors provide aspects of that, and some offer all three, but not for NodeJS. Dynatrace was the perfect fit.

We also really love the automatic alerts. Dynatrace alerts are based off of deviations from baseline metrics, which it is constantly collecting. We did not need to set thresholds ourselves. If something suddenly changes with our application or network that "doesn't look nromal", Dyantrace will tell us. It has been a breeze.

The pricing is a little high, but still cheaper than competitors because Dynatrace at least has pay-as-you-go. Others do not. However, the pricing is confusing. I wish it was more simplified when trying to price out moving to a yearly contract.

I also wish there was the ability to do alert filtering before it triggered an alert with PagerDuty/OpsGenie/Slack.

With nothing more than three commands, or a simple Docker container, we had everything running in minutes. Within one week, we had enough customizations to be production ready.

As mentioned before, we are a small startup. Implementing Dynatrace was a no-brainer. It would have taken us at least two months and hiring another SysOps person to get logging, monitoring, alerting, and APM implemented with cheaper or free open source solutions. It was far cheaper and faster to go with Dynatrace.

I use Dynatrace Client everyday. I also use it with web dashboards for monitoring performance of the systems and to trace our KPIs.

I have reduced our disruption time. With the automatic alerts, we prevent and better catch the root cause of problems. 

The most useful features are the measures out-of-the-box and the automatic alerts.

Furthermore, the web dashboard is very simple to use.

It is necessary to improve the integration with the product, Oracle Siebel.

Dynatrace must reduce the required resources for on-premise, because they are too high.

We sell it as a business partner. Our clients use it to test their systems before launching, seeing what is wrong before release.

Many clients have been able to reduce time on troubleshooting, since they find the problems before they launch the system, by running tests with Dynatrace.

The PurePath feature which enables you to see the path from click to database query. I think this is what makes Dynatrace unique from others.

Whenever there is a new version of the UI changes, it makes it hard to use, because we are accustomed to the old one.

DCRUM is no longer used by my team, due to lack of executive support.  Our primary use case was for post mortem investigation on application data flows.

We isolated to root cause on multiple occasions, identified performance bottlenecks in load balanced app infra, and delivered unparalleled usage and performance reporting for newly designed applications.

Agentless Transaction Analysis allows my team to granularly decompose complex operations and flows for business applications. Combined with SSL decryption, this capability helps my team to see the exact path a real user's transaction takes with meaning metrics captured at every hop.

Decodes on less used/popular protocols are available, but they should be included.  Additional investment should not be required.

No

In house

To discover the root cause of problems and improve our applications or environments based on very specific and detailed informations that AppMon brings to us.

Developers have started to consult us (the Application Support Team) more than before AppMon had been implemented.

PurePath lets us see the steps of a transaction and the time of each one, then we can know exactly what happened in what time.

I would like to know if classes and methods selected in "Method Sensor Rules" were changed in applications, and not depend on the developers to warn us. Today, if the name of a class or method that I previously selected in "Method Sensor Rules" or in "Sensors" were changed, I am not aware of this. I will not know until I need some information on Dynatrace AppMon. Maybe just a warning if a specific method or class in "Method Sensor Rules" does not exist anymore in the application is enough.