Dynatrace Reviews

We use this product for troubleshooting performance issues in our growing set of IoT portal solutions.

This solution has helped us to unearth quite a few issues that were present for a while. Also, it has helped us improve the performance of many of our applications.

The most valuable features are code-level visibility, real user monitoring, and response time statistics.

This solution could be improved with better compatibility with legacy applications.

In our case, we were not able to deeply monitor proprietary solutions such as Windows CE or some BI/ERP applications, which either got crashed or slowed down noticeably.

These kind of issues are bound to happen considering the intrusive nature of the instrumentation process (which is necessary to get good performance insights).

However, some of these technologies would often warrant quite an extensive amount of work to be made compatible, if even feasible.

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 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.

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.

Monitoring front-end for mobile banking within AppMon. We are using a balancer on NGNIX with a Dynatrace plugin to check availability by parsing logs.

Dynatrace helps to build business and non-business dashboards and the appropriate alarming on mail groups.

Native Java integration and building complex PurePaths between the front-end and back-end databases.

• It looks like it has already been improved with OneAgent, but it needs migration. 
• It needs improvement with proprietary protocols for the DC RUM part.

Our primary use case is for application monitoring. We have the AppMon product. It is performing well. 

We do not have a whole lot of organizational buy-in for the product yet, so there is a struggle in getting the resources to work on it to fully exploit the product's value. 

It will allow us to eventually become more proactive when problems start arising. We can see them before they happen and address them before there is any impact to our customers. 

• The overall application monitoring ability to do alerts. 
• The dashboard, so people can see what is going on. 

We do not know, because we are currently on the AppMon and we are looking at converting to OneAgent. Therefore, we are in that middle realm saying, "OneAgent, which is now Dynatrace, what is it going to buy us?" 

Then, we can say, "Well, what else might we need?"

Previously, we called support mostly about implementation issues. Docker was one which was early on and the support structure for Dynatrace. Typically, they were trying to help us figure out third-party applications and where the monitoring agent should be located. 

It seems to be very stable. We have not had any outages attributed to the product. We have not had any downtime.

We are a medium-size implementation. We have not grown a whole lot yet with the product, so we have not faced scalability challenges. It seems to be pretty straightforward to grow with it and add-on. They have guides to help you do this. 

The role of AI when it comes to IT's ability to scale in the cloud and manage performance problems will become more important, as we move forward in the cloud and with distributed computing overall with AWS.

Support is pretty good overall. Occasionally, you will get that support person who is not real responsive. However, for the most part, things have been very good. 

We have used siloed monitoring tools. We faced similar challenges using them to what we face today in that we do not have the management buy-in to get the resources needed to fully exploit the tools. 

I have been involved in the upgrade process in the finishing of the initial implementation. It was pretty straightforward.

I did not have any issues setting it up. The documentation really helped. If I did run into a question, I received a pretty quick response from our support people. 

We have not fully been able to get the full value out of the product. It is expensive compared to other things that we have had in the past. Paying that much and not being able to get the full return on the product is a downgrade. 

The technical team probably could help us learn more about the product, but some of the problem is on our side and not having the management dedication to fully exploiting the tool. 

The product is definitely worth taking a look at. Be aware that it is probably more pricey than other options on the market, but there are a lot of capabilities. Dynatrace has an eye toward the future and the computing and monitoring needs that we are gonna need for the cloud. 

If I had just one solution that could provide real answers, not just data, the immediate benefit for my team would be spending less time finding out what caused the problem and potentially being able to have those cases automatically routed to teams who could address them. Our team would be able to have more time to dedicate to other projects. 

Most important criteria when selecting a vendor: 

• Capability
• Stability of the vendor
• Market share
• Number of customers. 

Primary use case is to triage business applications and slow performance for our users. It is performing very well for now.

We have been a long standing customer for almost seven years, and using different tool sets from DC RUM to Gomez, and AppMon now.

It helps us get to the resolution quicker, and potentially the root cause, and at least understand what is happening for future identification.

The ability to really drill into performance issues and help our application teams understand what is causing the business's problems.

AI is really important because there are so many different tools that we have, so much data being collected, and being able to really sift through just general users is difficult. Therefore, using some type of AI technology to help identify and pluck out the important parts, it is critical.

We would like to see more external tool integration, which is critical for us. We are a best of breed, or at least try to be, customer for tools. 

We would also like to see all the good data in a single view across multiple tools, so that access to integration is critical. 

This would definitely gets us going forward in the right direction.

The stability is really good for what we have experienced so far. We have not experienced any downtime with our tool sets.

I have not experienced any issues scaling with the Dynatrace tools, however I have experienced scaling issues with other competitors' tools.

Over the years, they have been very good. Because of growth and popularity, it has been a little more challenging getting information, but they are knowledgeable once we do get them engaged. 

We have used siloed monitoring tools in the past. We experience a myriad of issues from getting them configured to providing useful information, and also sometimes licensing issues. Overall, the usefulness of the tool and helping us fix problems became the issues.

We were using other competitors' tools. Now, we have been migrating from some of those other siloed tools, but we do still have a mixture of tool sets. 

We are a longtime customer of Dynatrace. We started out with a single product, then brought in a second, and the third, so over time and seeing how the value progresses, we have substituted different tool set with Dynatrace tools.

The initial setup was reasonably straightforward. It was pretty easy to get deployed, and again, getting the value in a reasonable time. 

We had someone from the vendor technical support providing assistance as we deployed.

Right now, we are migrating many of our things to Dynatrace. We have already made the selection. Other competitors fell short. Integration flexibility and dashboard reporting capabilities were some of the key issues that we looked at. 

Do your homework. Test. Do your proof of concept(s). Be thorough in what you need and defining your reasons for looking at the tools. Even though everybody likes what they see, it may not be a good fit for what you are trying to accomplish. 

The tool sets are great. They provide good information. You can always improve them with better data. 

If I had just one solution which could provide real answers, not just data, the immediate benefit would be a single pane of glass perspective for the application in our environment. We have been striving for this consistently in the last seven to 10 years. It is absolutely critical. It is where we are working to get to: A single view which is telling us the problem, what to fix, and moving us on to the next problem.

Most important criteria when selecting a vendor: First and foremost is honesty. We have been in technology, and we, among many other teams within our organization, are a much more of a senior team. We have people that have been in the industry for 20 years or so. Just tell me what the issues are. We have the technical wherewithal to know how to work through them. Therefore, being straight up, honest, and having integrity as you are talking about the tools, demonstrating the tools, not only the highlights, but also the pitfalls and things that we need to work through. Have more transparency.

We are using Appmon and Gomez tools to monitor performance metrics in production systems. Appmon is used to monitor performance of production and test environments. We even use it to debug the results of performance tests using Appmon.

We have used Dynatrace for various projects. Everytime it has been really handy in identifying the root of the cause. We have used this tool to help in cases such as production performance outages and functional level issues.

PurePath is the most useful feature in the Appmon tool. It gives a lot of flexibility in identifying issues and finding the flow of execution. PurePath is also used to create many complex measures and business transactions as per our needs.

Addition of more statistical features, plus different time series modeling techniques, would really help for future versions.