Dynatrace Reviews

We use this solution for APM and synthetic monitoring, as well as real user monitoring and other basic host monitoring. We have problems sent to PagerDuty via webhook in Dynatrace. This also goes to our on-call center.

Debugging the worst transactions and other slow stuff is also done with this solution.

This has very much improved our organization. We now have a great solution for doing Application Performance Monitoring and doing synthetic checks.

The most valuable feature is the ability to perform synthetic checks for monitoring sites using click paths. Also, real user monitoring and basic host monitoring are really useful features.

Problem analysis is also great.

The user interface needs improvement. Sometimes it is not really clear how you can get to the right place, where you can find all of the information you need. It is sometimes really difficult to understand. If the user interface were made more intuitive then it would really benefit the product.

In Dynatrace, I really do not see any bugs.

Previously we used SolarWinds but it was really buggy.

Installation of OneAgent is really easy. We have installed this solution in a short time on nearly one hundred hosts.

We use this solution for APM Monitoring on .NET, Java, and NodeJS, as well as Infrastructure Monitoring for Linux and Windows Based Systems, Kubernetes and Docker on-premise as well as in AWS.

We perform automated monitoring using the Dynatrace API within our CI/CD jobs, and further, synthetic monitoring and HTTP Checks from different locations.

Dynatrace helped us to get a better understanding of how our services are communicating with each other, as well as better problem detection before something really breaks. We have been able to consolidate different tools, like standard host monitoring and synthetic checks.

The OneAgent with Network Flow detection is really amazing. It is simple to install, where you run just one command and you are finished. It automatically detects which applications are running, and injects the tracing automatically without any adjustment in our deployment.

The configuration options should be better accessible. Sometimes it is hard to find the right setting for what you want to change. In K8s deployments, the configuration of the Active Gateway sometimes changes, and when it's automatically updated the monitoring breaks and you don't know why.

This solution is primarily used for performance analysis and problem-solving.

Dynatrace helps us to improve overall performance and allows us to detect the root cause of an outbreak on our systems.

The most valuable feature is the indication of root cause at the moment there is a failure in our system.

The configuration of this solution is quite complex.

Our primary use case is to helps solve Java bugs.

This solution has helped us to improve application performance and reduce issue-impact with faster resolutions.

The most valuable features are Root cause analysis and User session replay.

Two things that can be improved are the licensing and the Business dashboard.

Web applications, primarily Microsoft MS-NET and Java-based applications, running on either IIS, WebSphere, and in lesser instances, Apache Tomcat or similar platforms.

Dynatrace AppMon has allowed a deep dive review of performance problems in near real-time for our primary external website and related web apps and web services.

PurePath view of methods and the call stack are extremely valuable for troubleshooting and performance review.

Dynatrace is a rapid release product, so new features or support for newer tech are being added all the time. Our primary wish list for RFEs or feature requests are additional integration options with ticketing systems. Although, we are able to work around it, 'ticketing' is not a core function of the product.

Use case monitoring of our shop floor systems. 

We use it for acceptance and production environments, which are SAP based.

We can report and monitor specific use cases which could not be monitored with SAP or other tooling. 

As of v.7.0, it is possible to use the web UI. Before that, it was too difficult using only a fat client

UEM can be used for user impact analysis and troubleshooting. We have applied this to prove that a specific issue originated from the back-end and was related to a specific user function.

Bring the interface to the same level as OneAgent. v.7.1 is a good improvement, but it has not been integrated into our environment yet.

One to three years.

We have multiple applications deployed in production across different technologies. We're using AppMon to monitor the services, the memory profiles, the traffic that comes through them.

It performs well. I have a team that works on configuring it, so they have a little bit of work ahead of them. It's not used across our development space, yet; so, not wide adoption.

It definitely helps, because my performance engineer, he can recreate a problem and he can give the developers what's happening, where to go look, all the information they need to be able to find what the root cause is.

The PurePath, being able to trace what's happening; to try to identify where the problems are and find the exact place to start looking.

We're thinking about moving to Dynatrace because AppMon is not scaling for us. One of the reasons I'm here at the Perform 2018 conference is to find out if there is a better way to use the product, not knowing that they were talking about the Dynatrace version. But to me, that's the logical place to go now.

So far, so good. Looks like Dynatrace is very simple to use. The sessions that we've been through here at the Perform 2018 conference, everybody has pretty much said installation is easy. Snap it in, a couple days later, you start getting information and you can put it right to use.

Scalability is the part that I'm looking forward to, because we're developing more and more microservices and, each time, for an AppMon license, you have to deploy it, you have to configure it, you to get charged for it. It's very time-consuming. Dynatrace is much easier, because it's auto-discovery.

We have a guardian that helps us. He's knowledgeable and gives us the right answers.

I think the role of AI, when it comes to IT's ability to scale in the cloud and monitor and manage performance issues, is huge. I have a directive to go to AI, shift left, go cloud, go microservice. All of that fits within a space where I don't have the resources to do that stuff manually, so let AI do it.

AppMon is our first APM solution. If we had one solution that could provide not only data, but real answers, if we deployed Dynatrace, and it got its own baselines, and then it told us, "We saw an anomaly, here's a problem ticket, somebody needs to look at that," that would be tremendous.

My most important criteria when working with a vendor are 

• support
• usability
• stability of the products 
• are they adopting to the upcoming technologies, because they're coming fast and furious? 

And so far, it looks like Dynatrace is doing all of that.

I would rate AppMon about six out of 10 because it's hard to set up, you have to have somebody very knowledgeable in the product. It's not intuitive. Out of a couple hundred people, I probably have 10 that know how to use it.

In terms of advice to someone who is looking at implementing a similar solution, I would say: Know your technology stack, know your applications, know what the roadmaps are, so you can make sure that you're implementing the right product to support all that.

We have a platform that is like an automation of DevOps. The company is getting into the DevOps environment and the primary hurdle for them is to choose the right tools. Our customers do not know if they get stuck with one tool if they could not easily move to another one. 

Our platform, what it does, is we give them all the tools that connect to what they want. In that process, initially we integrated the options, like ELK and Nagios into our platform. Then, some of our clients also wanted Dynatrace in it. That is how we got Dynatrace also on our platform. So, we integrated their APIs into our application, so now all our clients can use Dynatrace too. 

The most valuable feature is that I am getting business. My clients ask me something, I go to my technical team and tell them, "They want this and this." From my clients' perspective, Dynatrace below the dashboard is very good compared to other monitoring tools. The dashboards are a really cool feature when I get to talking to clients. I ask them, "Why Dynatrace?" Because I need to push the tools that I have in my application. Then, they explain the monitoring of Dynatrace, saying the rate of the updates and features. They want to go with Dynatrace.

Introduce a cool feature called "all monitoring", or something like that. It briefs an entire session for you, monitoring and replaying that entire session, so it becomes very easy. A cool feature which I can sell to my customers, which can drive more customers to Dynatrace.

For stability, our customers have no complaints. 

We increased our Client to experiment with the tools, so we could find the right tools. Some of my previous customers whom we encourage them to switch to Dynatrace, they had no complaints.

I do not talk to technical support. Our clients talk to Dynatrace. All our clients inquiries are directed to Dynatrace.

My job is not to rest because my whole platform's aim is to move on to next to the tools, like finding out what is right for their environment. Initially, if I would ask them to go for Dynatrace. Then, after using it for approximately one month, I can tell them to find out what they like and what they do not like. They can go on from there.

AI is very important. The world is moving toward an automation. In the future, it is going to be a new Ops world. There is no resource for sitting on the operations side, so there will be an AI which will be doing all the work.

When we implement the solution, the developers just supply the code and all the automation that happens behind them. That is what they expect. For example, it needs to do its work in a formulation, then determine what kind of resources you need for that and what kind of servers we need for all that. Thus, AI is going to be a big thing.

If I had just one solution that could provide real answers and not just the data,  the immediate benefit for the team is they do not have to spend time. So, the first thing is I don't have to bang my head about what is happening and where to find the solution. If I have something to use, which solves my problem. My life becomes easier.

Most important criteria when selecting a vendor: They should be very stable. Like most of the products in market, when they do updates, they break down. This will usually cause a slow down briefly to customers. This is where we will see if the product is stable or not. 

The vendor should avoid rapidly giving updates every month without doing testing, because if you see in the past with AWS (for example) when they released the patches for the Spectre and the Meltdown problem, it affected almost every company around 20 to 30 percent of the parts went down. The companies did not know that the patch was up like that. Transparency is important, and also, test the solution before you actually implement it.