Dynatrace Review

Shows the root cause and where exactly the error is coming from


What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the 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. 

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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. 

What other advice do I have?

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.

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Add a Comment
Guest