Dynatrace Reviews

We do a lot development in our company. We work with multiple servers, especially AWS and Azure. When we do these deployments and when we do these pipeline, we need to know what exactly is going on with the service and if there is an error. We need to know the root cause and where exactly the error is coming from. 

We have been using different kinds of monitoring tools in the past, such as, ELK and Nagios. This did not make much sense in a few of our uses cases. For example, there is an error in a deployment scenario, it does not show. It would remain difficult for us, as sometimes we could not find the root cause. When we switched it to Dynatrac, we could clearly see where the error is coming from and we could see the service performing well. We can also see the amount of usage, like the status. Particularly, the thing which we like about Dynatrace is its clarity.

It is clear. You can easily know where the error is coming from and the performance of Dynatrace is something which we have been really surprised with. Most of the other monitoring tools that we have used in the past have not been user-friendly, and most of the their user interfaces are terrible. With Dynatrace, this is not the case. It is very advanced when compared to other monitoring tools.

There are some cool features which they are trying to include like the tracing and the client side errors with the view. We could see the number of the problems where it is coming from, but we couldn't get in too deep to what exactly the problem is and what exactly the user is doing to see the error.

This a cool feature that they are trying to implement with video, which I appreciate a lot. It is not only that you are seeing that there is an error, you are also seeing where it is and what exactly the flow that caused the error. This feature has been announced it, and I was surprised by that, as it was exactly what I was looking for.

Compared to other tools, this solution is perfectly stable. The main feature with this solution is that you do not need to do a lot stuff. Everything is being done by the tool itself. Everything is in there for you. There is nothing much needed from your resources; it is all in there. That is the beauty with this solution.

Scalability is an important factor. At the same time, this is the Dynatrace solution we are talking about, it is really scalable when compared to other tools. We need to do a lot of stuff to make it work with multiple instances and multiple servers. So the scalability is there, but it is a headache when you do a lot of stuff and when you need to compare a lot of servers and do a lot of things. The scalability is very difficult to maintain. 

When things get reduced and the things from our side get reduced, as a developer, it gets much easier in order to scale. In this way, the solution is really scalable, and it is not difficult to get scalability with this solution. 

Regarding the customer support, they were very few instances that I have used them, but I would not say I use them regularly. I have only used them a couple times. They were really cool. They were really helpful. I got an immediate response, something not seen with other solutions. 

With this solution, you can always get in touch with support representatives and the developers if you want to, and you can get the solution directly from them. They are good about giving customer service, which I really like.

We have used different monitoring tools before when we had multiple problems. We would need to configure a lot. There are many tools needing an expert developer who had expertise in that particular tool. Therefore, we needed to have the proper resources for it where a lot of configurations were going on in, then one of the configurations failed. It is meaningless once your configuration fails and you can't find the error, or where it is exactly coming from. 

I was using ELK Stack. The thing with it is you need to do a lot of configurations where you need to maintain separate servers for each stack. You need to maintain three servers, which was a headache for us and it is also costly. You need to install agents in each server, which is the same for Dynatrace too. However, for the ELK agent installation, you need to configure a lot. You cannot just go execute a few commands and make the things work. You need to install, then configure it. It was pretty hard work as a developer, which was how we started to switch to Dynatrace, which is really cool.

Dynatrace is something which does not need many configurations. It is a just a simple way for you to install an agent in just three or four steps. Go in there in with just a few commands, and it is all set for you. In that way, Dynatrace is perfectly good for every cloud deliverer. 

I am happy with the Dynatrace solution. Dynatrace is a perfect tool when compared to other tools. 

AI is important when it comes to cloud. Every time you see a complex problem, you can't go in the server and find it yourself. You need expertise in order to do it. With the resources of a non-cloud person who has just been introduced to  the cloud, he cannot do everything that an expert does. 

With the evolution of cloud and an unattainable number of resources, such as everyone in your software company cannot be an expert with the cloud. This is where the AI comes in. It helps you a lot. It shows the correct path of what is happening.

AI is a huge, important factor, and it will be the dominating role in the coming future.

If I had just one solution that could provide real answers as opposed to just data, the immediate benefit it would provide would be to decrease the resources that you may need and not necessarily need to provide staffing for your resources to know the technology perfectly. You can reduce the cost of the training or for the things that would make a developer be an expert in the technology. So, it would reduce the cost while automating things, and it will make things work smoothly and perfectly for you.

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.

The primary use case is that we need to monitor our portfolio of applications. We need to pick out which ones are most important to us. Therefore, we use Dynatrace to help us understand how applications perform in different platforms.

We used to have a software perspective. Now, we will probably have more of a business perspective, as well. I am pretty sure we will be able to spread the use of monitoring information throughout the organization.

• Provides insights into the internal performance on parts of the application. 
• Various technologies
• Identifies problem areas and performance issues.

We might have a couple of technologies that we would like to see supported. I noticed a fairly new integration for Slack, I might want to see integrations into Microsoft Teams, or something like that, similar to what is there for Slack. Not sure what is already there.

I still need to learn is how to share information. There are lots of features to share information, but we need to learn to leverage that, both on the web browser and on the mobile app. How do I create the curiosity, not only technical people, but from the product owner's perspectives into their applications?

It is still new to us, but the stability is good. We have not experienced anything, both with the solution, but also with the support and the organization behind it. It works well for us.

It is very new to us, so we have not needed to scalability that badly. However, being cloud-based, I would suspect it scales as we need it to.

I have not personally used it, but a my colleague has used it. Our company gets quick response times and qualified responses, so that is good.

Dynatrace is still very new to us. We just switched from Admon to Dynatrace. We were having some technical difficulties with Admon. We had systems that were not supported, and they are supported in Dynatrace. That is one reason.

Also, Dynatrace, the new solution, is basically the future of what we need. Basically, our contract ran out (with Admon). We had to decide to extend the old contract or get a new one, so we decided to buy Dynatrace instead.

A colleague of mine did the initial setup. Compared to Admon, it is much easier to get some of the information. The challenge now is that we have a lot information with Dynatrace. The main task will be to sort through all the information and make sense of it. That is the major difference.

We actually looked at a couple of other competitors, but we know Dynatrace, the organization, supports us. 

We looked at the features of other tools, and Dynatrace's features fit us best. We also have good support in places, like Scandinavia. We use Red Ocean, a Dynatrace partner, to support us and that has worked out well.

Take a close look at what you need. Do you need a technical perspective or a business perspective? What do you actually expect to get from your solution? Then, pick your solution based on that.

AI is still new to many, so we have to learn to use it, to navigate, perhaps even to trust it. With a product like Dynatrace, we will start learning to use it and get experience in how it works for us, then we will probably start trusting it. It is something we can't look into, but we will see that it does what we think it should do.

If I had just one solution that could provide real answers, not just data, that could provide an immediate benefit for my team, it would be to save time. We would save time debugging things ourselves. We would save minutes and hours of precious time until we are back up and running again.

Monitoring of the hybrid solution, having application components spread over various datacenters. Having the insight from any channel, whether it is mobile apps or a website, we have everything covered. This gives us the capability to proactively monitor performance, but also give valuable insights to the user behaviour. 

The alerting mechanism where you get millions of dependencies analyzed, in one alert or "problem" as Dynatrace calls it. We are getting focused answers to issues in production, and moved away from the ops concept of "alert suppression", which historically has ignored seriously business impact due to over alerting. 

In short: The IT Ops game has been lifted, and silos have been broken down between traditional dev and ops.

The one agent technology and autodetection. 

That it made it possible to get the monitoring up and running fast. Therefore, we could focus on the value that Dynatrace provide. First, you harvest the low hanging fruits of failures and performance issues. Then, you have the foundation of implementing Dynatrace in your ITSM. 

In short: Time to realizing the value is short, maybe hours.

The thing with Dynatrace is the speed of releasing new capabilities and features. The one thing I am really missing is the final Azure dashboard. Further, I hope Dynatrace will release an on-prem API synthetic test soon, as that is really desired.

No issues.

No issues.

I used SCOM. I left due to moving to a cloud strategy.

I did not do the calculation.

Evaluate all the corners of the data Dynatrace provides, including outside dev and ops. The hole ITSM space can be ignited with Dynatrace integration, like CMDB synchronization.

I did not evaluate anything but Dynatrace.

Try it out. This is literally one tool to rule and distance any other.

Dynatrace facilitates great live performance monitoring, allowing us to easily and visually detect problems before they become a large impact issue to the business. It is not uncommon to detect and quickly use various drill down options such as PurePath to quickly identify and provide initial analysis on problems.

• Creating different dashboards
• Sharing dashboards with edit permissions
• Simple classic but effective UI (unlike some modern UI's out there that have too much white-space)
• Wide variety of dashlets available to monitor various services/components

• Either use less system resources and be faster or use more resources to pre-compute the PurePath on recent X minutes of data
• More flexibility with refresh times
• More UI options

Overall, it's quite stable.

We haven't had a chance to change the scale much and will probably not scale up by any meaningful factor.

Customer Service:

It's great.

Technical Support:

I haven't had to use it a lot.

Overall, it's very easy to setup on the client side.

We currently use Dynatrace in conjunction with another APM tool as well as a synthetic monitoring tool.

I would highly recommend it.

User Experience Monitoring (UEM) helped identify customer segments, which were creating a frustrating experience on our website. With revenue being driven primarily from the digital channel, it was imperative that we focused on improving performance. However, UEM helped us to triage the issues, and gradually lay down a plan of action. With greater visibility over customer behaviour and experience, it helps drive revenue streams.

When we started with Dynatrace, there was a lot of data available. However, the challenge was looking at the right ones at the right time. Our organization was reeling with issues on a particular set of variables, which were recurring and correlated. The need of the hour, was customized dashboards. Custom dashboards are easy and quick to develop in Dynatrace, and we could, therefore, easily get started with regular monitoring of key issues with these quick customizations. I rate it highly because as an end user, it is important that I get data in the way I want to see, comprehend and analyse. The ease of doing that was what won us over. On top of this, incident alarms helped automate incident management mechanism to a large extent, thereby reducing human intervention.

We have been able to customize incident alarms.

Better intelligence in terms of identifying business transactions, would be appreciated. Also useful, would be pointers to recurring issues and auto incident management.

I've used it for two months.

No issues encountered.

No issues encountered.

No issues encountered.

It's high.

This is the first solution like this that we've used.

It was quite straightforward to implement.

We used a vendor team to implement it, who had a high level of expertise.

• New Relic
• AppDynamics

The company uses it for a lot of things. Obviously, we're using it mostly for application monitoring, and that covers both application performance and availability. We're using it for checking how things are performing and making sure that they're running and running properly and there aren't errors or issues. That would be the main thing. 

We're also using it to monitor servers, do some infrastructure monitoring, make sure there're enough servers are running and that they've got available disc space for monitoring CPU and memory, et cetera. 

The solution is stable. 

I find that the AI on offer is useful, as it's good at identifying problems. You do need a bit of customizing, however, even in its sort of vanilla form, it's pretty good at identifying problems and the root causes of those problems and whatnot. 

The installation process is straightforward.

They're generally going in the right direction and they're quite responsive to feedback. You can vote on features and whatnot. If enough people vote for a feature, they'll get it put in. 

The solution could be more seamless. The user interface could be better and they could offer more integration. 

We'd like it to be more user-friendly, which, in our case, might be a big ask as we have a fairly complex environment. 

How long I've used the product depends on which version you would classify as the product. The current one, under this name, has only been out maybe three or four years. However, I also used the older version before that, and that was something called AppMon. Therefore, I've used it for a while at this point. 

The solution has been very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

I can't really comment on the scalability as we're in a relatively small environment. We don't have a massive number of servers on-site. I am aware of people that run it in massive environments, however, I can't make a comment on what it's like as our site is fairly small.

We might have ten or so active users. 

Technical support is very good and very responsive. We're quite satisfied with the level of service on offer.

Before Dynatrace there was another Dynatrace product called AppMon. Before that, we used to use the company's own solution.  

The initial setup is easy and pretty straightforward. It's not overly complex. 

The main issue is that, due to the fact that it covers so much space, the navigation can be long-winded. It can take a lot of clicks to get into where you want to go, however, it's covering a lot of information.

On the site that I'm on, on the Dynatrace site, there's really just me that's doing the technical side of Dynatrace. I'm the one that's keeping Dynatrace itself running and whatnot. That said, even in bigger environments, there's probably only one or two people that are looking after Dynatrace itself. It's really solid in that regard. 

I don't really get involved in the commercial side of things and therefore cannot speak to the aspect of licensing, such as pricing. We might be on a three-year contract that gets renewed.

While my organization is a reseller of Dynatrace, I actually also work on it myself. 

While the deployment model that we're using is on-premises, there is a cloud-based version of it as well.

We're always using the latest version of the solution. It gets updated automatically, and therefore it's pretty much the latest version.

I'd rate the solution at an eight out of ten overall.

I would recommend Dynatrace to others who are looking into implementing it.

We primarily use the solution to monitor performance and point our issues in the user experience of applications - specifically mobile applications. We are able to more clearly identify problems.

We have a workflow in which we use Dynatrace with the developer and QA. We can test the application with load testing, duration testing, and then identify the applications ready for production. Sometimes, due to the findings, we have to go back to developing. Dynatrace it's really useful in that case due to the fact that we are able to avoid releasing a product that is not ready yet to go public.

The AI on the solution is excellent. The product can be used to identify situations or elaborate on some problems and find the root cause of issues and how they impact applications.

The initial setup is easy.

The solution needs better integration with networking appliances such as rotors, switches, and firewalls. It needs to work better with SNMP protocols and the like.

Dynatrace should put a little bit of effort into releasing documentation. They have a lot of new features that come out regularly. Pretty much every month there are new features. However, its information on those new features is scarce. Sometimes there's technical implementation information, however, it's really small. There needs to more information in order for the documentation to be useful. Some users are not that technical and need a little more help to understand the new features.

They should automate some settings. 

I've been using the solution for eight years at this point. It's been a while.

The stability is really good. I don't find it cumbersome and I haven't had any issues with it. There aren't bugs or glitches. It doesn't crash or freeze. It's very good.

The scalability is really good. We were able to migrate to the new version almost seamlessly. We can use other functions or features of the software. It's really easy to add up and keep seeing different options and features. 

We work with some companies that are quite sizable. We work with companies that are in the food industry as well as three of the largest national banks. We also work with smaller companies as well. The solution can work for a company or pretty much any size. We alone have 30 or more clients that include companies of every size.

Technical support has been really good. Truthfully, we seldom use it. However, when we use it, it's fast. It's accurate and they are really good. They know their stuff. We're satisfied with the level of service provided to us.

We've had clients that have used other solutions in the past. Some of them used to use SolarWinds. Some of them have App Dynamics. There are others as well, including some software that isn't well known. Many use open-source tools and Dynatrace. 

The main difference and the main role of Dynatrace is the AI. No other vendors have AI integrated. Many also do not have such a simplistic installation. The automation of Dynatrace is great as well. You don't have to go to the application and modify it in a file, for example. However, Dynatrace can be a bit more expensive than other options.

We've found the initial setup to be quite straightforward. It's really easy. A company shouldn't have issues with implementing or deploying it.

Basically, we just have to assemble an environment, a QA or the development environment of a specific application. It usually takes two or three hours just to set up everything and keep it running.

We use about five to 10 users for an installation. Usually the IT Manager and the DBA security managers and also developers. We even have some product and marketing managers. They use it to identify users.

We don't need the assistance of an integrator or reseller. We can handle the implementation ourselves.

Although I see the value in the solution, the pricing can be a bit more expensive than other options.

As we're using the cloud deployment model, we're consistently on the latest version of the solution.

We are a reseller. We both use it ourselves and offer it to certain clients.

The best thing you can do is try it. You can try it for free. You can try it in an environment you know really well. That way, after a trial, you can decide if it really will work for your company or not. 

On a scale from one to ten, I would give the solution a solid nine.