It provides a nice graph, and we can see where everything goes. If it could go agentless, that would be great.
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.
How has it helped my organization?
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.
What is most valuable?
The graphical interface is helpful, as it illustrates things well for anyone who wants to know about the information it provides.
What needs improvement?
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.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How is customer service and technical support?
I have not used the technical support.
Which solutions did we use previously?
It is a brand new environment. They didn't have anything before.
What was our ROI?
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.
What other advice do I have?
There are no comments to display