Dynatrace Reviews

We use Dynatrace to monitor the API performance of the server.

Dynatrace has an auto-baseline and uses AI to monitor the performance of each API. The response time is related to the baseline.

The most valuable feature is the auto-baseline because I don't have to set it with Dynatrace. With New Relic, we had some problems with the configuration.

I would like to see the same features as in the New Relic Insights in the dashboard. That is the only thing I want to see improved in Dynatrace.

Dynatrace is quite stable. I don't have any issues with it. With Dynatrace we need to upgrade and restart often. New Relic is more stable than Dynatrace.

I have not had any issues with the scalability of either New Relic or Dynatrace. They are both quite scalable.

Currently, we get the vendor support directly. Their support is adequate.

Last time we were using another APM and the company discontinued the APM product, so we had to switch.

The initial setup of Dynatrace is quite easy.

We implemented the installation ourselves without any issues or problems at all.

Our most important criteria when selecting a vendor are the features and local support of the agency. Those two along with pricing are very important. 

The reason we eventually chose Dynatrace was for the automatic (auto-baseline) of detection for the API performance issues.

We use New Relic as well in the same facilities.

I will rate the software a nine out of 10 because they are able to help solve our issues for us even though we don't understand the system fully. 

To make it a perfect 10, Dynatrace needs to implement the features from New Relic in the dashboard so that I can monitor my own performance. Even though New Relic is not as good as Dynatrace, I have to understand my own system. I set each parameter manually before every launch by five minutes.

I would suggest to prospective buyers to evaluate both Dynatrace and New Relic to see which features are best for your company. 

If you are not sure about the system requirements, choose Dynatrace. If you understand your own system and know by seeing a network outline exactly what you need for support, then choose New Relic.

Our primary use case for both Dynatrace and AppDynamics is for application performance monitoring (APM). The main reason for having application performance monitoring is, when we see something is running slowly, we can immediately look to see where the issue is at before our systems crash on us. So, one of the major roles it plays for us is the ability to keep our system performing in peak shape.

Our ability to see issues coming, then quickly isolate and correct problems was our main use of Dynatrace. We are not there yet with AppDynamics. It has been ten months, and we are still spinning our wheels trying to set it up and figure out how it works.

When collecting data with Dynatrace, we saw every single transaction that happened in real-time. Whereas, with AppDynamics, they take snapshots, and we only see a tenth of the information that we did with Dynatrace. While the information is there, if an issue with an application happened in-between snapshots, it would not be readily identifiable. You would have to go hunt and peck for it. We don't have time for that.

Using Dynatrace, we collected application metrics within three hours, in most cases. The majority of our triage were within three hours, then we were able to discover the root cause of issues.

With Dynatrace today, you have a single agent. You stick it on a server, and it doesn't matter if it's Linux, Windows, etc. It is a single agent and executable. You run it, and it injects itself into your collecting data. This is compared with AppDynamics, which on some of servers, we have had to install as many as four different agents and configure them all individually, trying to collect the same type of information.

The dashboarding for Dynatrace is ten times easier to set up and has more options of what you can put on it, especially if you are in a single payment class environment.

With Dynatrace in our environment, the managed server required root access to run. As a government agency with tight security, this has been an audit concern for us. A major area of improvement for Dynatrace would be to make it so the program does not need root access to perform. AppDynamics does not require root access to the servers. Once they are set up and configured, they can set their end run without root access.

The number one area of improvement for AppDynamics is to simplify their agent install. Instead of having four or five different agents to get all the different things that you need with different pieces of information, they need to figure out how to put theirs into a single agent, like Dynatrace has done.

We have not found AppDynamics in our environment useful at all. We are struggling to try and make it work. AppDynamics is for applications that are static. In our government agency, we are too dynamic. Everything is changing constantly, and AppDynamics does not work in this type of environment.

The stability for Dynatrace is probably 85 percent. We had enough issues where one of the services would just stop running, then we would have to restart it. Not very often, but it happened.

With AppDynamics we haven't been able to use the system long enough to determine its stability.

Dynatrace is very scalable. We grew it over the 12 years that we had it. So, that has proven that it is scalable. 

AppDynamics is scalable as the environment grows. However, we are still in the product's infancy, so we haven't seen this happen yet.

A company with a single application over multiple locations, like a retailer, but only needs to worry about one application and monitoring it, this is the perfect fit for AppDynamics. If you have an organization with more than 40, you definitely want Dynatrace. AppDynamics is not a viable product for an organization with lots of applications.

On a scale of one to ten, my experience working with the AppDynamics onsite people and offsite support is maybe a five. I feel that they don't want to take responsibility for the areas that AppDynamics is lacking in. When things don't work in which they were sold, then they want to tell us that it is our environment more than their application not functioning correctly. 

Whenever we had issues with Dynatrace, you could get Dynatrace support on the phone, and they were all over it. They would get into our machines, then take screenshots or look at the performance of the systems while it was running. They wrote custom patches to help us resolve issues that we had. I would rate the support that we receive from Dynatrace as a ten out of ten. 

We have been using Dynatrace since 2007 and AppDynamics for just about a year. We have not been using them concurrently. Dynatrace was not renewed, and management decided that we would use AppDynamics. This decision was beyond my control.

With Dynatrace, the installation and setup were a piece of cake. It could be accomplished usually within fifteen minutes, and definitely, within a half hour of deciding to do it. 

A big difference that we found between the two vendor is in setting the system up and getting them ready for production. With the latest version of Dynatrace, it took three days and we had it in production. We are still trying to get AppDynamics in production since last May.

With our Dynatrace system, it required three servers and the program when we installed it on the servers. It was straightforward. You just clicked, clicked, and clicked as it went through the setup, then you were done. 

With AppDynamics, we are now on eight servers to make it function like it should. We are ten months into it now, and we're still trying to get it right. We have AppDynamics folks onsite to help us with it. It is just difficult to implement. There is so much to it. 

I sat down with one of their architects to decide how many servers that we needed, how they need to be spec'd out, etc., and that is what we built. Then, when we stood it up, and it didn't work, some other personnel from the AppDynamics team came in to look at it. They said, "None of this is correct. You are on the wrong this and that." 

Thus, we did not have consistent information and support from AppDynamics when implementing the system. However, it is up and running now.

Our annual costs were about the same for both AppDynamics and Dynatrace.

When learning Dynatrace, we brought in Dynatrace people to come onsite and take my team through a week long training. We did that two or three different times. They offered this type of training. They also have online training out on their community that I could set up for my team members. The effectiveness of that training was about 75 percent. 

With AppDynamics, they have provided some online training. The take away from it (from my team) has been maybe 10 to 15 percent. The training is geared more towards sales than using the product for what it was intended. It boasts the features and selling points of the AppDynamics product instead of the ins and outs of how to use it once it has been installed in our environment.

I would definitely recommend Dynatrace. I have the benefit of having used it for so many years. It takes less infrastructure to set it up initially. It's a single agent engine. You just set the agent up and run it, then it configures itself. It goes out and finds all your processes with everything that's running, configuring itself. The simplicity of the infrastructure and simplicity of setting it up, then actually using it, along with setting up your dashboards to monitor your metrics is much better. There are more features than the AppDynamics dashboarding.

I would rate it Dynatrace as a ten out of ten. 

At the point of where we're at with our AppDynamics experience, I would rate it as a five out of ten.

Dynatrace is an extremely helpful APM solution in large, complex environments, whenever we need to have an integrated vision of our users, infrastructure, and applications. It excels when we need to do all this with the lowest resources possible, with the best data quality, across all layers, and with the least management overhead. 

The first time I came across Dynatrace, I simply remember the WOW factor. Being a performance enthusiast since the mid 80's, I cannot remember more than a handful of such technical experiences!

Dynatrace excels in troubleshooting scenarios. You do not get samples or gaps. You get the real thing. That is absolutely important when troubleshooting the strangest situations.

Focus on root cause analysis has dropped significantly for the importance of alerts. I was used to be drowning in alerts, but now have refocused. I still have them, of course, but now they are about minor things. I see myself getting rid of them very soon.

The most valuable feature is Dynatrace's commitment to bringing in new features. It is very difficult to keep pace with the new developments that are always occurring.

The OneAgent technology is one of the most important features. You install it, no configuration, and it just does all the stuff for you. It automatically detects whatever is happening, and even gets to automate JavaScript injection across different web server technologies. You can have tag management, but you can even forget that, because that is fully automated, too!

Given the full-stack approach, you are able to view from the end user perspective, almost down to the bare metal. It gives you all the way from the user perspective, network experience, web and application server view, application detail, process detail, operating system detail, and you even get to manage virtualization and datacenter support.

Dynatrace is capable of following all user actions across all monitored infrastructure, even to systems not monitored, but interconnected. This technology is known by the name PurePath, and being able to do this sometimes feels like magic. I have been told, time and time again, by very knowledgeable IT personnel, that this is not possible. Sometimes, you have to see it, to believe it.

One of the most promising features is the AI capability. I have seen some of its capability in production environments, and it is pretty impressive! It is not a marketing buzzword being abused, but it actually works. Being able to offload problem handling and root-cause analysis, and get to the point analysis of complex systems is something that I have not seen with my eyes, and in this depth, in any other IT solution to date. 

Dynatrace's online presence in APM "education" is second to none. Viewing the YouTube online videos, hearing the PurePerformance Podcast, getting to learn in Dynatrace University, and following the documentation is like being in performance heaven! You just can't grasp it all!

In the new Dynatrace solution, support for legacy applications is still not there. Given there is excellent support of legacy applications and protocols in the Appmon & DC RUM offers, they have the knowledge to put it there. Knowledge that their competition simply doesn't have.

One to three years.

Not seen one stability issue since I been dealing with it.

No issues with scalability. The solution is multi-tenant and based in Big data technology.

What impresses me more is the ability to be able to analyze 100% of all activity going on, and do that with so low overhead. I have not been able to observe more than 1% overhead, despite Dynatrace saying that it can be slightly higher in some situations. I sometimes get the impression that overhead might be negative (underhead?), because you can get rid of inefficiencies like log dumping, that typically have high (disk and CPU) overhead.

Support is just great. Part of it is public, so everyone can check it out. Dynatrace direct support is even better, and you sometimes get direct answers from the teams that are implementing the functionality.

I have worked with other APM, IT, and UX monitoring solutions before. None of them is even near what Dynatrace has to offer.

Never seen anything so complex be so simple to install.

Directly implemented.

Pricing can be high, especially for Portuguese standards. But as one says, you get what you pay for.

Setup cost is very low considering that it is an almost totally, automatic process. Installing SaaS or Managed is only some minutes away. Given that there is no configuration involved in the agents, you can develop how many you want per hour. It only depends on your IT deployment strategy. TCO is thus much lower than expected. Licensing is very interesting, as you pay only for what is being monitored. A lot of things are given away for no additional cost. If you have a great IT consolidation, it will be pretty cheap. If you have a lot of servers, it will be heavier.

Since you cannot manage what you cannot measure, I do give the most importance to data quality. This is priceless. If you manage based on bad or incomplete data, you are leaping into the bad decisions direction.

The return might just be immediate. You install it and after minutes you are getting the full data in. The other day I compared Dynatrace to another APM solution, and the other person had been struggling nine months to get the data out. When he saw what Dynatrace did out-of-the-box, he simply could not believe it.

Finally, be prepared to be surprised! It is very fast pace. The Session Replay and the Augmented Reality are just two recent examples. Almost every day I get some new perspective in this field, like AIOps, and it just keeps getting faster! 

I use this solution for application monitoring.

The functionality needs improvement.

We do not see any major impacts on the stability of the product.

I would need to explore this further because I have not tested it further than our needs.

We have not needed tech support.

It is on the high-end of the price range of products.

I advise that when you are looking for a new product, consider:

• Features 
• Accuracy 
• Consistency

We use it to get the network stats and know how many clicks happened on both the front-end side and back-end side, then drill down on debiting to obtain the stats around that.

Dynatrace is working fine right now. It is working as we expected.

We can dig into Dynatrace to analyze data, then know where the user is going based on user navigation. 

Performance-wise, we can see if there are any issues. Then, we can dig into them.

It gives complete stats of the user and what they are doing.

Because we are financial, there are certain things that we cannot put on the cloud. However, that is a given fact, not only for us. It is a given fact for any financial company because of PCI compliance. Because of PCI compliance, companies don't take the risk of putting data in the cloud. Otherwise, we have had a very good experience with the cloud.

The stability is good. I have not seen any issues.

I would rate scalability at least an eight or nine out of ten.

Everything is excellent with technical support. Some of their personnel are our main point of contacts. They are always in touch with us.

The integration and configuration is very easy.

Purchasing through the AWS Marketplace is excellent. 

We did not evaluate any other products. Top management said. "Just go and use this."

It functions well. We are getting good support. It gives us everything that we were looking from it.

We use the on-premise version and have just begun onboarding the AWS version. 

We use it for application performance management (APM).

It alerts us, or can detect, potential problems which are building up. Then, it let us quickly adapt our websites.

• Dashboards
• Problem detection
• Troubleshooting

It is very stable and reliable.

We use a cloud version for everything that we look into, so we have had no issues. Scalability is working well.

The technical support is excellent.

We were previously using AppDynamics, then we switched to Dynatrace because it has more functionality, better additional components, and better management of problems. It also has a good AI.

The integration and configuration of this product were very easy.

It works quickly with all of our servers, databases, and load balancers. We are now testing it in AWS with AWS features.

It's helping us stay alive, afloat, and scale up as we need.

The pricing and licensing are very expensive.

Try it. It is a good product.

We have used both the AWS and on-premise versions. They are about the same for us.

The primary use case is for application performance management. So, we are using it to identify outages of different parts of the application as well as how we can make the application more efficient and rightsize it.

We can see down into the layers, such as with databases. We can see database queries which are causing problems. 

We can see CPU usage for different containers. I can do a run and see what errors exist in containers which are causing problems. We can rightsize containers on the fly and understand what is happening with our Docker, microservices, etc.

The most valuable feature is it has AI in it. The artificial intelligence (AI) engine in it is able to do alerts and some good analytics. During outages, it is able to identify and correlate where the actual root cause of a problem is. This connectivity allows us to be able to see a bit further into the application down through the layers. If it is a problem within AWS, a problem within a container or something that a user did. We are able to see and coordinate that, then we are able to tell the developers how to fix it.

The GUI has the most room for improvement. Sometimes, it can be a little cumbersome to find things and be able to create your own views, or be able to dig in and understand where things are.

Some additional features would be the ability to break out some of the permissions and allow some additional or different ways to tag services, events, and different things which run. We want to push down the ability to do that, so developers and other folks can get in there. Currently, more permissions are needed to be able to do certain things, and we want more people to be able to use it, own it, and understand it.

We don't put very much stress on it. We could probably stress it some more, but we don't have enough systems right now on it to stress it. For the most part, the ships don't cause as much stress. 

We are going to have it on about 40 ships around the world which will run it independently of our AWS platform. Those are don't stress it too much. We will probably stress it at a certain point, along with AWS, but we still very much growing the platform.

It can scale very well and very high. We don't need it to scale as much right now. It is able to absorb a lot of the systems that we have with the agents and and the API Gateways. It seems like it can scale very well when we need it to, so scalability is good for us right now.

If we needed technical support, we usually call our account team to help us figure out where the errors are, whether it is something with an agent or management servers.

It is pretty easy to integrate it into the AWS environment. You give it a username and password and it asks some basic permission. It can pull a lot of information very quickly. We are able to correlate more and provide more data for it. So, it was easy to integrate it into that environment.

We have it running on AWS. It integrates pretty well there. We have it on Red Hat Linux servers, as well as Windows servers. We have it running on VMware where it integrates very well. It understands these productions and understands our platform. It is able to read into Docker containers and all the databases that we run. However, it is limited as far as how many of a certain type of database that we can have, but for the most part, it runs pretty well and integrates very well.

It has been doing a good job of alerting us to issues. It has been very helpful and effective at identifying how we can do things to make our infrastructure and application a little better.

We considered AppDynamics, Datadog, and Crashlytics. We even considered things like Splunk for different pieces of it.

We chose Dynatrace because we needed something which could run both on AWS and VMware on our ships that might lose their Internet connectivity. This product gave us the flexibility of being able to do both. Dynatrace had the ability to run independently, so we could access it while it retains information.

A PoC is the best way to go. Put it against an application and go through the paces of tagging, analyzing, and alerting on it. You can understand what it does and how it does it. Give it a very complex application, so you can see how well it works.

We use the on-premise version because we have it running on VMware. We also use it on AWS to manage our systems on AWS for production and for our non-production environments.

Our primary use case for the product is going through logs and tracing through what has happened.

In general, it has helped me go through different logs more easily when something breaks.

Being able to quickly go through logs and figure out what is happening.

It needs a better way to figure out how to dig deeper into the details, e.g., sometimes we have to wade through multiple logs, etc. 

It has been stable. It doesn't break.

Its capabilities are good.

We have a couple AWS accounts that we are running on the cloud. Then, we have a lot of on-premises applications, as well.

The technical support is readily available.

The integration and configuration of this product in our AWS environment is pretty seamless and easy to configure.

We don't really integrate it with anything else.

Purchasing through the AWS Marketplace was a pretty straightforward process. We had no hiccups.

I think the pricing is at a fair value for what it is.

We looked into New Relic and other logging solutions. 

After doing our research, we figured out that Dynatrace was the best for us.

It is a very useful product. 

Depending on your use case, try all the solutions out, then figure out which one is best.