Dynatrace Reviews

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.

We log everything. Anything that goes wrong, we want to make sure that we are able to see the reason why. Therefore, we check metrics around CPU usage, RAM usage, etc.

It's a different way of thinking. Before, we were with a big, monolithic app in the beginning before fully transitioning over to AWS Services, which has been breaking it down into a microservices architecture. It has allowed us to look at it and debug out from a different perspective. Previously, we were going in and looking at server logs, logging into SSH toolbox and debugging manually there. It puts everything in one place, so everyone has one center has one center tool to look at.

For what we're using it for, and having seen the other side of things, where we were debugging and looking into logs manually, then trying to run an analysis on them, it was a painful process. Looking at it from that perspective, it makes things a lot more user-friendly if you are using a tool like this. That is just been my experience with it personally, which is nice. 

It is tool for the job. It does what it's meant for and does what it is supposed to, which is good.

From a debugging perspective, when we look at things, we want to ensure that we know exactly what is happening at a certain point in time. It provides us a reference for being able to go back and look at data at a certain point, analyze it, then determine if something was the root cause. 

When compared with other tools, the experience needs improvement. I would like them to build out the interactions and make them friendlier.

So far, so good. I know there are a lot of competing tools out there. For what it is and what we've used it for, it has been good.

I have never had any issues, so I haven't had to contact them.

There is time savings. People's times have been cut in half using this solution because we were previously doing a lot of that manual work. Now, it's a lot more automated, and the data is just there.

We used a different tools out there, like New Relic. Dynatrace is good, but there are features which other tools provide that it doesn't.

Do some research. There are a lot of tools out there with a lot of features, which people have bought into it. Make sure to get the right tool for the job. When you do bring a tool on, take it for a trial run first, then see if it is giving you the value which you are looking for.

Our primary use case is monitoring.

Previously, some of our web publications were so hard to find that we would be constantly monitoring it using a graph and a type of installation tool. Now, it is very different. Dynatrace has reduced the time it takes to detect the service failing in production.

• You don't have to configure it. It just needs to be installed. 
• It locates services on its own, providing us good visualizations of them.

They should include more mission learning into the product and provide additional performance metrics for application learning.

The stability is good.

Scalability is good. 

It reduces our efforts to identify services failing in production.

Our experience purchasing through AWS Marketplace was good.

It is perfect for application monitoring.

The integration and configuration of this product on the AWS environment is good. We are using the on-premise and the AWS versions, which are pretty much the same.

I work with a product called Rancher, which integrates really well.

Primary use case is EMI, which is application monitoring. Our enterprise management infrastructure is supported by Dynatrace.

Dynatrace has been catering to AWS, and we moved into AWS. This resulted in us being pleased with the product.

Dynatrace has solved our problems.

The view it provides for default analysis is very nice. The way in which it showcases how the metrics have been captured and how lucidly that they are displayed. This is a good thing to have from a technical and non-technical perspective.

For the manage services, they work on CloudWatch logs and are given CloudWatch logs only. I would like more collaboration with AWS and insight into CloudWatch services. This would be valuable, especially when detecting the fault of the root cause analysis. It would make the process go faster. Essentially, more integrated services with AWS would be of help.

It is stable. We have not lost data.

It has quite a sleek architecture with respect to the number of instances that can become an agent. 

As for its environment, Dynatrace is ready to scale. Our environment is huge. We have EMR clusters ranging from 100 to 200.

We regularly connect with the technical support and obtain input from them. They are nice to work with, so we have been happy with the service.

We worked with architects for the best way to configure our Dynatrace in AWS. We selected the managed architecture, and there are less configurations and costs of adoption with Dynatrace.

While it is quite good in respect to its functionality, there are few area in regards to pricing that they can look at how to possibly change. I have heard it's costly.

We did evaluate other vendors, like Datadog, who were also good. However, Dynatrace was implemented earlier, and we continued to use it because it was satisfying all our requirements. 

Our requirements include:

• Overall monitoring.
• Managed services of AWS.
• Monitoring AWS Lambda.
• Monitoring Amazon EMR clusters.
• Getting an understanding about the different set of services that we are on. We have a managed architecture supported by Dynatrace, so we could adopt them very fast.

Dynatrace is pretty good as they are the market leaders.

We started with the on-premise version. Now, we are moving onto the AWS version. From the perspective of analyzing Dynatrace, it was able to do the EMI for all our data services. It has worked out well. We have been happy with it.

It can monitor your entire infrastructure on AWS. I don't see an option why you should not use this product. If you don't have AWS as a requirement, then maybe re-evaluate. Otherwise, I am confident in the product.

Dynatrace is a 21st century APM tool designed and developed keeping next generation technologies in mind. We implemented it in our dev environment first, and the results were awesome. We got firsthand RCA as soon as we finished implementation.

We are in implementation and adaptation phase. It would be very early to comment on this, but we are very hopeful.

• Ease of deployment, except few hiccups in agent installation. 
• The overall rollout experience was great. 
• Ease of use and root cause analysis laced with the AI engine. 

The problem evaluation feature is an awesome idea, but bit difficult to pick up initially. Please make it a little more intuitive.

Dynatrace is nextgen tool.