Dynatrace Reviews

Identifying performance bottlenecks on load testing environments. Before launching new code into production, it is imperative to know if performance issues will arise.

It prevents (together with performance testing) production performance issues which usually result in customer complaints or system downtime.

The product capabilities all together are valuable. You get a good insight into what is going on inside your code.

• Monitoring asynchronous code requires manual instrumentation (most of the time). 
• Some autodiscovery capabilities would be nice in the tool.

Application monitoring on our clients environments, including microservices, JVM, .NET, and many other technologies

Real user monitoring is one of the best things in solution. The possibility to analyze any particular user session is wonderful.

• We have some issues with react user sessions. 
• We sometimes have to run plugins on docker containers.

The product is really fast to implement and gives customers instant value. This is important, because it reduces costs on the implementation.

We are implementing software on our clients' environments

We use it to monitor and debug issues for both our infrastructure and our code. Dashboards are quite handy to get a quick glance at the health of our system.

The dashboard allows us to monitor and proactively act upon any breaches in the threshold for our infrastructure. We have also had a couple of cases where Dynatrace identified issues within the code, such as memory leakage.

PurePath technology allows us to drill down deeper into the system. This helps us isolate and rectify problems more quickly.

• The installation process had quite a few moving parts, so it was a little tricky getting everything to work in first go. It required a solid day for the requested Dynatrace onsite technical person to get everything set up. 
• Nginx monitoring service did not work out-of-the-box, so we had to tinker with it for quite some time.
• Beginner video tutorials would really help.

Overall, it has provided improved stability to our system both within prod and non-prod environments.

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.

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.

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.

I recommend Dynatrace to all of my clients for Server Monitoring/APM. It makes it so much easier to proactively solve problems before they become big headaches, and easily pinpoint the root cause of an issue.

Transparency and visibility into application performance, errors, incidents, etc. helps to foster a collaborative environment.

The ability to drill down from an alert into a problem and pinpoint the source of an issue saves my client teams hours of time.

The user interface is complicated, but recent web versions are getting better all the time. The improvements and new features in each release are great.

At the moment, we are focusing on internal IT processes covering the entire application lifecycle. Later, we would like to work on EUE.

• Deep insight to code
• Quick root cause analysis
• Quick bug fixing

Dynatrace provides a clear view to application code; it reviews code to decide where to place check points to collect information. Based on that, it is able to specifically identify where in the code it is experiencing either an error, issue or performance trap. This also provides third-level support with a clearly specified place for resolution without needing to re-create the error. It reduces the amount of time required for communication between all of the support layers, as they can share the same info - what has happened, what was result, where it happened - so in the end, it leads to quicker issue resolution.

Technical support is well-skilled and competitive.

Dynatrace was chosen as our first solution.

Initial setup was quite easy and straightforward. The solution by itself assigns a place for sensors. You just need to properly set ports and IPs.

We implemented it almost entirely in-house, with some remote vendor support.

Pricing is based on the number of servers monitored, so for big applications, it is a bit expensive.

First, make a detailed analysis of the purpose for such a tool, and then define detailed requirements they plan to achieve.