Dynatrace Reviews

The visibility that it provides is most valuable.

There should be more visibility for network performance monitoring. There should be more metrics for things like 5G and IoT. That would be the main thing because they've moved more to mobile performance rather than fixed networks.

I have been using this solution for over 10 years.

Its stability is very good. There are no complaints.

It is pretty scalable.

I haven't had to deal with them too much. I would rate it as average. It has been good enough, but I haven't had too many moments where I had to reach out. I would rate their support a four out of five.

It is straightforward. The agents are pretty straightforward to set up. I would rate it a four out of five in terms of ease.

As compared to New Relic and other providers, it is more expensive, which is its biggest disadvantage. Its biggest advantage is its capability. It is more feature-rich.

My advice would be to try it before you buy it. I would rate it a strong eight out of 10.

Overall, it's a good platform.

The solution has a very good user interface.

The product can scale.

It's fairly easy to set up and manage.

It will be great IF we could show (automatically, from the dynatrace dashboard) to the customer how much they are reducing costs, doing more business and no environment's stopped. 

We've been using the solution since 2015. it's been about six years or so at this point.

No worries about that.

The solution can scale, however, if you have a large amount of infrastructure you will need to pay more. I find that if you start with just a small part (the critical part), you'll better understand why you need more of it and scaling will come naturally. It's not just about managing the servers and applications. It's about the user experience too.

I haven't really dealt with technical support. However, our tech team is quite capable of handling any issues should they arise. 

We are also familiar with IBM SOLUTIONS.

The solution is very easy to implement and easy to administer. It's not overly complex.

Our IT team is capable of handling any implementation our clients need.

What I try to say to my customer is that, okay, it's not so expensive, if you could see the return of investment you will get. However, in Brazil, we have some difficulties when it comes to showing these numbers to the customer (they don't have the actualized numbers). It might be better, in the current market to just try to sell it to IT instead of across departments. 

The pricing is quite high and many customers do not want to pay for it.

Dynatrace it has been our best APM Solution.

We are an IBM partner and are beginning to work with solutions such as Instana as well. We're also partners with Dynatrace.

In the last three years, we've started to grow our customers and have new use cases. I believe due to the movement towards digital transformation, we have more opportunities to show the benefits of a platform like Dynatrace.

We are using the private and public domain from Dynatrace, however, we have customers and major financial customers who prefer to use either private clouds or a private environment. We believe that it doesn't matter where they are. I'm happy with this model, as we could get faster results in two weeks when we are implementing Dynatrace to our customers. It's faster to implement on the cloud.

I'd rate the solution at a nine out of ten. We've been quite happy with its capabilities overall.

We use Dynatrace for monitoring channels like mobile banking and internet banking.

It is being used in a commercial organization for monitoring two high priority services. If you are changing some PCs or doing some updates, it provides some responses. It has been very useful for us.

It is really comfortable and easy to use for application monitoring. We are able to see and go deep into the problem. We didn't have any issues with this product.

Its pricing could be better. Dynatrace has an option to monitor the end users to see what they are doing, but it required a separate license and had an additional cost. It was coming out to be expensive, because of which we didn't use the feature.

I have been using this solution for about two years.

It is stable.

It is scalable. We are currently using it only for four channels, but we want to add more servers. Next year, we may extend the licensing for eight more servers.

We never had a problem, and we never had to create a case with Dynatrace. The company from which we buy this product also helps us in using it in our organization. We don't have support problems. 

The initial setup was really easy. We had the first testing environment in just two days. We tested how the agents work, and it was easy.

I would recommend this solution. In Georgia, it is already very popular, and many companies are using it for applications and external channels. 

I would rate Dynatrace a nine out of ten.

We use this solution for our customers for a wide range of tasks and for application optimization and such. It can be used in a performance test environment where developers run a new release to check they're headed in the right direction. I'm a senior analyst programmer and we are resellers of Dynatrace. 

This solution is very powerful for the end user. It's a valuable solution but because of the cost, we try to explain this to our customers that they are not only buying a monitoring tool. Dynatrace offers a really important approach because the tool is able to monitor a lot of different features. 

I think that they have to make improvements to the product, particularly with regard to the infrastructure monitoring which is not yet complete. Although it's very powerful for application and end user monitoring, the infrastructure needs to be significantly stronger. Configuration is also not so simple and that could be improved. 

This is an expensive solution which makes it difficult to sell to customers. Even though the features are good, the price is too high. At the moment, we are able to sell the product, but only to really big companies. It's quite difficult to sell to a mid-size company. 

I've been working with this solution since 2007. 

The product is stable, they generally provide an automatic update on the tool every couple of weeks although we tend to test and then do a manual upgrade. There have been a few issues but the support is really quick to solve problems.

The technical support is very good and they have a live chat. You can open the chat from the product and check any issues. They are highly skilled. Sometimes the issues are more complex but even then they deal with it professionally. 

I have some experience with APM Elasticsearch. It has a module that you can activate and then make an analysis. I also know some of the other tools but they don't compete well with Dynatrace. 

The initial setup has improved over the years and is now quite straightforward. There's a lot of work involved to customize the entire environment.

Anyone looking to implement this tool needs to take a 360 degree approach. If you take that approach then everything will be easier because you can see all the stakeholders and the value that the tool can give. If you approach it from only one angle, such as from the developer or operations perspective, then it would be very difficult to get an idea of all the features that the products has. This tool is very complete, but the price can become a bottleneck for some.

I would rate this solution an eight out of 10. 

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.

Currently, at my organization, we have DC RUM, Gomez synthetics, and AppMon. We are getting ready to PoC the OneAgent technology. Our use case for OneAgent will be containers monitoring, AWS monitoring, and microservice monitoring. Our organization currently has a digital services team that will be doing a lot of this cutting edge stuff and our architecture is not being fully monitored by the current stack that we have. We also have a tool called ScienceLogic that we use with our Ops bridge and we have Splunk. Therefore, we are really looking for the OneAgent to fill in the gaps that we are not covering. 

Out of the gate, I can tell you that just changing the agent model from having to go, "This is a Java, this is a .NET, this is a web, or this is an app," And getting rid of that to having the OneAgent is an improvement. Then, being able to monitor anything, literally anything on the infrastructure, that will be huge for us. 

Another thing is the log analytics. We have to work with the Splunk team. We have a very fractured organization, so anytime an application team wants log monitoring, they have to work with the Splunk team. Anytime we want log monitoring we have to work with Splunk team, it is a paperwork process. It is not that they are not nice people, it is just that it takes a really long time, and by then, the problem may be gone.

We really just need the immediate log analytics, because we might not need long-term analytics all the time. Like Splunk, they do awesome data analytics, but sometimes when we are troubleshooting an issue, we just need to look at where the problem is.

I would like better plugin support, because they are constantly asking us to do plugins, saying "Yeah, we can do that. Use this plugin."

Then, the moment something goes wrong with that plugin, I have no way of getting help. They recommend, "Contact the plugin author." You are kidding me? Those guys do not have any obligation to respond. They wrote it, but they do not have to support it. 

I do have concerns about stability. I have heard there are gaps being mentioned and I think that we will lose some features. I am not entirely trusting that this is fully-baked yet. I am probably going to go back to my organization and say we really need to do a PoC and we need to get on the train. However, I am not stepping down AppMon or our current DC RUM for another year or two, because this really needs to mature.

I am not worried about scalability. OneAgent is going to more scalable than the clunky old solutions that we just put to bed.

I evaluate technical support on a criteria of:

• Did they help solve my problem?
• How long did it take them to help solve my problem?

I have not had very positive experiences in the last year. I found them to be arrogant, rude, not solving my problems, and not interested in solving my problems. 

They are very insulted if you ask them questions. They refer you to read the documentation. I am like, "Well, I already read the documentation and that is why I am asking you a question." 

"Google that," is not the answer that I want hear out of tech support, because I already googled it. So, I have been rating them very low. It is actually the one pain point I did bring up to my sales engineers and sales support. They are aware.

Our organization just dumped HPOM and the plug was pulled on it in 2017. We are getting ready to sunset SiteScope and HPE BSM. The really siloed monitoring tools are archaic and high maintenance. The infrastructure is too big and moving too fast to be constantly updating old-fashioned tools.

What I really am excited about is that they just announced that it will be doing session replay for the DC RUM part of it. We currently have IBM Tealeaf and we hate it. We hate its guts. Our management hates it because we rolled it out to one application and it cost us over a million dollars to do that. We wanted to roll it out to a second application, and IBM wanted another million dollars. We already have the on-prem and a trained administrator. That was the licensing that they wanted that million for.

Dynatrace just said the session replay that DC RUM will have, it will put IBM Tealeaf out of business. Thank God, because that solution literally is from the 90s. I am not kidding you, it was coded in the 90s, and it is extremely brittle. It is hard to maintain, and it is clunky. If they can get that replay to be smoking, then they will make so much money. All the Tealeaf customers will stampede over here.

We stood up AppMon five years ago. It was not straightforward; it was complex. 

We paid for a Dynatrace guardian to be onsite for two years. The guardian rocked. We really loved the guardian. If we had not had the guardian there, we would not have had an adoption rate like we got.

Thursday and Friday last week, I got pulled into what they call a triage team. They had a problem in production where all these people were in a war room with all these fingers being pointed. Nobody had the full picture. I am using AppMon, which performed beautifully and management was super impressed. Just using AppMon 6.5, the visits, being able to drill down, and find the answers there worked. However, if I had had the OneAgent, DC RUM, and SaaS solution altogether, I would not have been in there for two days. It cost our company so much money and they still do not know what the answer is.

This is an expensive solution, but it is also worth the money.

My organization evaluated Nagios and a start-up company. Then we evaluated Dynatrace as well, and it just outperformed the others.

I am really excited about the AI that I am seeing out of the OneAgent because I was just at the IBM conference last year. The IBM AI is still pretty much a toy and I have not really seen the rubber hit the road with their stuff, but the rubber hitting the road is here with the Dynatrace AI. From what I have seen, it will be a key tool set for us just to pin down problems and get answers immediately. 

Most important criteria when selecting a vendor: Everything that they are doing is right, except tech support and plugins.

We purchased Dynatrace to give us an end-to-end picture of transactions from the end-user, all the way back through all the infrastructure, and tag it all together - and it's worked out great.

The main benefits are that, obviously, we can see the transaction throughout the entire infrastructure.

One of the things that we're embarking on is, we're trying to measure the impact to the business of infrastructure events and incidents, rather than using gut feeling or emotions of whether we feel there was an impact, or asking our customers, how were you impacted. We have data now to prove it. So it's just taking the emotions out of it and just providing the facts of the impact, of the incidents or events.

The most valuable component of it is taking that guessing out of troubleshooting problems. We no longer have to rely on an architect, or an application person, or someone's memory of how the transaction moves throughout the infrastructure and the different dependencies that it has on it. We can see it right there and we find out more that we ever imagined.

We like the user's experience piece: being able to see, from the browser perspective, the user's behavior; being able to answer questions from our customers about why such and such happened, why the performance was slow, why we had an error. Many of our customers are business partners. They're not a customer online that couldn't shop or something. They're customer service representatives, maybe, or a customer service team, that is experiencing slowness, so they're reporting it very quickly and letting us know. We're able to see those transactions and it's helped with our mean time to repair.

I'd really like to see more dashboarding abilities. The ability to do workflows within dashboards, being able to start at a high level and click into it with custom dashboards. I think most of the time, we are creating our own custom dashboards, and I'd just like to see more ability with that.

I would also like to see it baselining more metrics out-of-the-box. We have a lot of rich data, but if someone says, "Well how did that look last week?" If you're looking at a problem and you see, for example, a long SQL statement, is that the root cause, or is it always slow; that kind of thing. It's difficult to take that and say, "Oh the SQL statement was fine last week and it's now slow and it started slow at this specific time." So, it's difficult to get historical data, unless you know in advance what your problems are going to be.

I feel, overall, it is very stable. We have some response-time issues from the product or from the UI, and getting all that massive data back. But overall, the stability, the availability of it, is good.

I think scalability is what we're struggling with. I would say it's okay, but there's a little bit of room for improvement.

We've spoken with tech support several times. We've used them to answer questions and to help us get more value out of Dynatrace. We've also uncovered bugs and they've been able to help us identify those and support has come out with fixes for them. It's been good overall.

We didn't really have a short list. We had another solution that we were using and it just really wasn't fitting the bill anymore and Dynatrace just slipped in. We just started evaluating it and we liked it, so we just went forward.

I think with anything that's of a massive scale, there are complexities - even just trying to understand the product. Obviously it's a new product and you're trying to architect something you don't know. There are definitely challenges and hiccups that occur with that.

I think, overall, the implementation of actually installing was fairly easy. Most of the problems, really, were organizational problems on our end. You know, change-windows being very small, and the testing requirements that we've put in place, caused the implementation to take a while. But the tool itself was pretty easy to implement.

When it comes to the nature of digital complexity, and the role of AI when it comes to IT's ability to scale in the cloud and manage performance problems, we're not really using the cloud very much, so I can't really say for the cloud piece. But I do think that these transactions are more and more complex, and there's so much data. That's one of the great things about Dynatrace is there's so much data, and it's also one of the most difficult parts about Dynatrace, is there's so much data. So having that AI to bubble things up for you, so that you're not searching for a pin in a haystack is definitely the future, I think, for Dynatrace.

We have used many, many siloed solutions and still do. It's hard to give  those up. The problem is, obviously, everybody is looking at their own silo and looking at their own monitors and, of course, it never looks like it's that silo's problem.

One solution that could provide real answers, and not just data, is really what we're looking for. It takes the guessing out of monitoring and everybody is seeing through the same window. That's what our team is designed to do, come up with answers, not just provide a lot of data. Obviously, we can send out data to folks, but they're not looking for that. They want your opinion of what the problem is, or what the answer is, not just charts and data. So it's very valuable for our team.

The criteria we were looking for when choosing an APM solution were the ability to gather metrics on a lot of different technologies and solutions. I was on more of the technical side. The financial side was kind of smoke and mirrors for me. I just evaluated the technical aspects and was looking for a solution that would give us an entire picture of the transaction.

I would recommend Dynatrace, of course, but I would just mention again, that you have to kind of think about the story that you want to tell. Determine, in advance, the metrics that you're going to want to show over time, for that historical view of data.

We use it primarily for performance. We bought it so we could be more proactive versus reactive with our customers. We are using it for anything from database monitoring, performance monitoring, end user experience monitoring, etc.

It is performing great. No issues so far. It is fast, and there is no overhead.

We are not in the cloud yet. We are moving to the cloud. This is one of the reasons why we bought Dynatrace. We know Dynatrace is going to OneAgent with the its product. That was a big part of our decision of buying Dynatrace, so when we move to the cloud we will have something to monitor.

I am getting emails every day about how great this application is. We are rolling it out to a few teams. They are using it. They love it, and it is easy for them. They can just get right in, look at things, and say, "Oh yeah, there's an issue right here." I got an email today from another team saying, "Hey, this helped a customer with their slowness issue," So, it is good. 

The most valuable feature is being more proactive versus reactive, because before customers would call us with issues and we had no clue what they were. Now, we can call or alert them that there is an issue and we are working on it. That is the most valuable part.

I would like to see single pane monitoring.

We have had no problems with stability. Though, we did have a couple issues in our production environment getting the UEM working. It would crash some of our applications. Agents were injecting the JavaScript twice so it was bringing down our apps, but we worked with support, and they fixed it pretty quickly.

It scales well. We are going to be able to use it for everything we need.

They have a very active community.

I have used CA Wiley. It was slow and cumbersome to use. It was good, but it just did not have anything like Dynatrace has.

I have been a performance engineer for about 10 years. Using Wiley, you could look into the system. I moved to this company and went to SEP Con in San Diego where I met with some of the guys from Dynatrace, then I knew the company needed this tool. 

When I moved to this company, they did not have any production monitoring or QA monitoring, so that is where we have started Dynatrace. This is what we have needed.

I was involved from the PoC to the setup, then roll out. I am not an admin, but I was part of all it.

It was pretty easy. Our middleware architect, he had no problems with it. We rolled out all our environments (QA and prod) in about three months.

New Relic and AppDynamics were on our shortlist. We picked Dynatrace because of the training and ease of use.

Dynatrace has great training available. It is easy for everybody to use. Anybody can go out to YouTube, watch a video, and figure out how to use the piece that they need. All these other application monitoring tools, they are all basically the same. They are going to give you the same data and just present it a little bit differently, but Dynatrace goes above it with their training.

If you had just one solution that could provide real answers, not just data, the immediate benefit would be time. Everybody would have more time to do something; get things done a lot faster and go out on the golf course and play golf.

Most important criteria when selecting a vendor: With this vendor, the most important piece was the amount of training which is available. There are so many YouTube videos. The website has so much to offer. None of the other APM tools had anything close to it, so that was our number one criteria.