External reviews
External reviews are not included in the AWS star rating for the product.
Useful for small things, less for serious debugging
What do you like best about the product?
Can easily set up and catch example data from runs. Can sometimes be a good alternative to going into the code and adding logs - doesn't require us to deploy and wait for logs to go live. UI is good and intuitive.
What do you dislike about the product?
When your flows contain a lot of data, and you want to explore all of this data, rookout doesn't catch all of it by default, and you are required to click "Collect more" which still doesn't collect all data you usually need if it's huge. I would prefer it to collect 1 example of full data from one flow/run instead of trying to collect partial samples from many flows. As a result rookout is mostly useless if you're trying to find, for example, if a specific entry exists in an array of size 100.
The most serious flaw is that conditional breakpoints a lot of times don't work (in Wix's case I never managed to create a conditional breakpoint by metaSiteId or requestId).
Also missing a feature to "collect sample from one run and that's it, stop".
The most serious flaw is that conditional breakpoints a lot of times don't work (in Wix's case I never managed to create a conditional breakpoint by metaSiteId or requestId).
Also missing a feature to "collect sample from one run and that's it, stop".
What problems is the product solving and how is that benefiting you?
Don't have to pollute code with logs. When debugging in production saves the time it takes for a log to deploy (and the time to write the log). As a result I'm writing less code that's not relaed to business logic.
- Leave a Comment |
- Mark review as helpful
Debugging systems in production, and used the pycharm extention
What do you like best about the product?
The ability to add breakpoint on the fly, make them conditional, the support we get from you
What do you dislike about the product?
The Pycharm Extention takes too much space in the screen and not so intuative
Rookout make our programs slow (a bug that we discuss about with the support)
Rookout make our programs slow (a bug that we discuss about with the support)
What problems is the product solving and how is that benefiting you?
Understand what happened with the data in our system and investigating complex problems.
Some fiddling around
What do you like best about the product?
Easy to use, nice features, low entry level.
What do you dislike about the product?
Maybe somewhat better customization is appreciated.
What problems is the product solving and how is that benefiting you?
Debugging in cloud
Dynatrace review
What do you like best about the product?
Provides end user response times from applications. This is something we have not been able to get in the past from other tools.
What do you dislike about the product?
Does not provide native database host monitoring
What problems is the product solving and how is that benefiting you?
Monitoring and alerting for business applications.
Very good Application Server Monitoring tool
What do you like best about the product?
Easy Plug-n-Play for the Monitoring dashboard User, once configured.
What do you dislike about the product?
Overhead on the underlying H/W and network
What problems is the product solving and how is that benefiting you?
System Monitoring
Basic understanding
What do you like best about the product?
Powerful software that will notify us if something is about to go wrong or has already
What do you dislike about the product?
The learning curve of the application. .
What problems is the product solving and how is that benefiting you?
Detecting issues before it becomes and issue
Recommendations to others considering the product:
Requires a decent knowledge to unlock the power of the application
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?
It provides us a reference for being able to go back and look at data at a certain point, analyze it, then determine if something was the root cause. However, the experience needs improvement.
We log everything. Anything that goes wrong, we want to make sure that we are able to see the reason why. Therefore, we check metrics around CPU usage, RAM usage, etc.
How has it helped my organization?
It's a different way of thinking. Before, we were with a big, monolithic app in the beginning before fully transitioning over to AWS Services, which has been breaking it down into a microservices architecture. It has allowed us to look at it and debug out from a different perspective. Previously, we were going in and looking at server logs, logging into SSH toolbox and debugging manually there. It puts everything in one place, so everyone has one center has one center tool to look at.
For what we're using it for, and having seen the other side of things, where we were debugging and looking into logs manually, then trying to run an analysis on them, it was a painful process. Looking at it from that perspective, it makes things a lot more user-friendly if you are using a tool like this. That is just been my experience with it personally, which is nice.
It is tool for the job. It does what it's meant for and does what it is supposed to, which is good.
What is most valuable?
From a debugging perspective, when we look at things, we want to ensure that we know exactly what is happening at a certain point in time. It provides us a reference for being able to go back and look at data at a certain point, analyze it, then determine if something was the root cause.
What needs improvement?
When compared with other tools, the experience needs improvement. I would like them to build out the interactions and make them friendlier.
What do I think about the stability of the solution?
So far, so good. I know there are a lot of competing tools out there. For what it is and what we've used it for, it has been good.
How is customer service and technical support?
I have never had any issues, so I haven't had to contact them.
What was our ROI?
There is time savings. People's times have been cut in half using this solution because we were previously doing a lot of that manual work. Now, it's a lot more automated, and the data is just there.
Which other solutions did I evaluate?
We used a different tools out there, like New Relic. Dynatrace is good, but there are features which other tools provide that it doesn't.
What other advice do I have?
Supply chain
What do you like best about the product?
The integration with other softwares and applications
What do you dislike about the product?
Needs new versions and upgrades to meet customer needs
What problems is the product solving and how is that benefiting you?
Easy reporting tool and helps to provide efficiencies.
Technology Leader
What do you like best about the product?
The product offering is extensive and maintains to be best in class with monitoring.
What do you dislike about the product?
The cost model is more expensive and has removed features which were relevant with the AppMon product.
What problems is the product solving and how is that benefiting you?
We required more insights into our technology, with ability to track the core metrics of our application.
Recommendations to others considering the product:
N/a
showing 1 - 10