Dynatrace Reviews

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.

We use Dynatrace for application monitoring.

We use this product with the goal to improve our abilities.

The most valuable feature is the monitoring of application performance.

I would like Dynatrace to be more flexible and user-friendly. They could do more in-depth analysis of the application monitoring. Also, they also could do some type of anomaly detection with positioning and have better integration with AWS.

So far, the scalability has been okay. Our customer base is hundreds of thousands.

The product needs a lot of the support, especially on the consulting side and post sales. You will also need an administrator.

I was not involved in the decision-making process. However, there are more competitive products on the market, which are more user-friendly, feature-rich, etc.

Research into similar products. 

It adapts well for integration with other products in our environment.

We don't use it for AWS.

We are using it track how the data flows throughout the entire AWS environment and seeing if there are any road blocks in between and trying to fix those. Dynatrace is really good at illustrating those. It provides a nice graph, and we can see where everything goes. It is easy to explain both to the people that work with it and the customers who want to see where their data is going.

In terms of tracing where the data is going, some clients don't want it to hit a particular instance, or even worse hit a database that is not part of what its designed for. Therefore,  it makes sure everything is where the customer expects it to be. It is a great tool for that.

The graphical interface is helpful, as it illustrates things well for anyone who wants to know about the information it provides.

If Dynatrace could take out the controller that would be great. It is one less thing to install right now. Though, I understand why they would need it. 

The less stuff that you have on the instances which are running on the actual apps themselves are better for people that watch user products. So, if it could go agentless, that would be great, but I understand why Dynatrace would need it to capture the points. However, every time we spin up an EC2 instance, we have to slap an agent on it and that is more work.

I would like them to make those agents and controllers as small as possible. That would be great. Or, if they could remove them entirely, that would be great too.

I haven't had any major issues with stability. Sometimes, the controller feels a little overloaded if you have a lot agents running, but that's just a matter of sizing things up.

The scalability ties into the Dynatrace controller, because there is just one which talks back to your on-premise. While it is nice to have just one point to talk to, when you start having a lot of apps and things trying to connect to the same thing, it can cause some issues. I do get it, it is just a networking thing along with design.

I have not used the technical support.

It is a brand new environment. They didn't have anything before.

In terms of explaining to a customer how their data works, it has been a great tool. Instead of trying to draw it out, then hoping that is exactly where the data goes.

Try it out. They are other tools on the market, but with this one, the graphical interface is what I like the best. If that is what you really want, definitely go for it.

While working for an MSP, these customers' use cases vary - in most cases, we must do the fault domain to identify who is responsible in order to fix the root cause.

One use case: A customer blamed our data center, stating it caused broken sessions for their Citrix users. After looking at the network traffic data with NAM (ex. DCRUM), it was easy to identify issues within ISPs at Asia, and not in our data center here in Europe.    

All of them which measures performance and availability. If you don't measure, you don't know. Looking at the data patterns and trends, you can also find out abnormalities in the whole ecosystem, not just in the target application.

Reporting and dashboards could be better, compared with competitors. However, Dynatrace has excellent API for data mining but requires extra reporting tool.  

The primary use case is monitoring and diagnostics for production marketing usage.

The visibility into the application's performance helps the executives and managers by using easy dashboards. Our engineers are also super happy with the ability to drill down and fine-tune based on issues which we have seen. A bunch of issues with OpenID were easily investigated, then we were able to fix them quickly.

It has been a very enabling tool for us, especially for my team. The visibility that it provides through the application's behavior allows us to find trends based on our customized metrics.

• Alerts: The alerting system is really nice.
• The ability to drill down and pinpoint issues.

The new Managed Edition is too complex. I feel like a fish out of water. From the on-premise version to the AWS version, our initial use has been very complex. 

For the integration, I use a hollow testing tube called Performance Center. I would like the ability to integrate with it. This would be a good feature. While I believe it is there, it needs to be fine-tuned.

I'm pretty impressed with the stability. 

With the AWS version, you can access the updates through the browsers, not worrying about the tick line. 

With the on-premise version, you need to use the tick line for updates. There are times when architects, who do not use the product constantly, find their stage and production options out of sync, then they need to have two tick lines on the same system.

There was an issue on-premise. We were trying to troubleshoot a production issue. We had to run a bunch of queries for different time frames to see where the issues were and how recently they had been seen. This crashed the Dynatrace server.

We are now moving slowly moving in installments of the AWS version because our environments are not large enough right now. So, we haven't tested it yet.

I have only heard positive reviews.

We went with Dynatrace because of its ease of use and it is feature-rich. It helps you to drill down into bottlenecks and find issues. When you have highly integrated systems, it gives you an extra lens through your whole ecosystem.

The Dynatrace team helped us with the integration and configuration in our AWS environment.

There have been many advantages in terms of production and issue resolutions.

The product is pricey, but it is feature-rich, which is why we probably haven't looked away from it.

We are also using New Relic. Our product teams keep explore new options to see what is out there.

I prefer Dynatrace over New Relic because there are better features.

I would recommend Dynatrace Managed because it has more features, and go straight for the AWS version because it is simpler to manage. It can also be accessed through the browser. 

We previously used the on-premise version, but have switched to the AWS version, which has more features.

Our primary use case is operations monitoring.

When something goes wrong, we have visibility into the system, can find the issue, and quickly get things back up. This was previously much harder to do.

It gives us visibility into the product and what we are doing operationally.

As we move into using more AWS native architectures, it should support everything that we want to do. We don't want to adopt another tool.

The solution has been really stable.

So far, scalability has been fine. We have not seen any issues related to it. It looks good.

We had a good experience working with their technical support.

We were previously using CA Wily (CA APM).

The technical support helped us spin it up, then we received training on how to use it.

We compared it to AppDynamics. While I did not chose Dynatrace, from a technical standpoint, AppDynamics and Dynatrace are pretty comparable. I liked how both of them worked. Because we were moving more onto the AWS platform, Dynatrace was more compelling because they were right there with us.

Kick the tires. Figure out how it fits your use case.

Our primary use case is application performance monitoring.

It helps with monitoring KPIs.

• Security
• Automation monitoring

I would like them to add serverless capabilities, because everyone is going there.

The stability is rock solid. We put a lot of stress on it.

The scalability is amazing. It is the best. One of our customers is a massive healthcare customer.

I am a partner, so I know people in technical support who I can contact.

The integration and configuration was easy.

We have seen ROI with this product.

The price could be improved.

We also evaluated New Relic and AppDynamics. We chose Dynatrace for the hybrid version and price.

I want to tell people about its hybrid security capabilities. A lot of people have legacy experience with the tool, so it is valuable. They would not have to reinvent the wheel.

We use a hybrid environment, so we have to use the both AWS and on-premise versions.

The product is integrated with Splunk and ServiceNow. It integrates easily with them.