External reviews
External reviews are not included in the AWS star rating for the product.
Amazing product for debugging on the fly without stopping!
What do you like best about the product?
The fact that you can put a breakpoint that captures all data without suspending program execution even in the production environment is just mindblowing! It's also very helpful to use with API development as you can hook up local files/repos and use these special Rookout breakpoints to debug your API!
What do you dislike about the product?
The initial setup and configuration may not be as straightforward. While the documentation for this is thoroughly written, it's not super simple to follow without direct guidance.
What problems is the product solving and how is that benefiting you?
It solves multiple problems. The first is that it solves the issue of debugging the production code without affecting or stopping the application running in production. The second problem it solves is the tediousness of having to put a breakpoint in the local instance and suspending execution to see the data at the breakpoint, which can alter the default behavior of the application.
- Leave a Comment |
- Mark review as helpful
Great out-of-the-box working tool that solves complex cases and saves lots of time
What do you like best about the product?
The fact that it works out of the box, the setup/configuration step is very minimal and it solves such complex problems amazes me. It removes the need of adding logs or similar things to debug complex bugs, therefore it saves not only time, but also money, cause pipelines of deploying such debug-related code take a lot of computing and time to run.
What do you dislike about the product?
The UI is good but perhaps it could be more intuitive, i.e. sometimes the breakpoint doesn't appear immediately, it could give us some suggestions on i.e. not putting breakpoints on lazy vals that could corrupt the data being collected, etc.
What problems is the product solving and how is that benefiting you?
Bug solving in production. i.e. a wrong type is used in the code and that causes the code to break. This makes me more productive cause I have to spend less time writing code, pushing it for review, deploying it, etc.
Easy to use and helpful tool
What do you like best about the product?
Basically is easy and faster to use and deploy. You are able to analyze very quickly an issue in your services without deploying any extra infra o tools.
What do you dislike about the product?
I don't have a lot experience but maybe it will be useful to have differents deploys in different tabs
What problems is the product solving and how is that benefiting you?
To have all the infra locally to try to debug an issue. You can deploy in Rookout easily to have a first analisis.
Great tool
What do you like best about the product?
The biggest upside for me using Rookout is that all the debugging logs are shown without stopping the application, allowing other developers to use the environments while I am debugging. It is also easy to integrate, allowing me to debug quickly. Overall it improved my debugging experience tremendously.
What do you dislike about the product?
Could be better if there was a way to allow breakpoints to have different default values such as time limit
What problems is the product solving and how is that benefiting you?
Rookout helps me debug more efficiently
Best for tracking the bugs in you app
What do you like best about the product?
The best thing about Rookout is that it allows Live Logging and Debugging. I can see and debug what is happening on my app in real time. Best for testing those untraceable bugs.
What do you dislike about the product?
The User interface is quite confusing. And free plan has quite limited functionality, and the pricing also seems high compared to other alternatives like New Relic and Dynatrace.
What problems is the product solving and how is that benefiting you?
My Web application was crashing without any reason. The bug was hard to trace because the underlying algorithm was tested against all the possible cases, and it was sometimes crashing. Later using Rookout, we found out for which file it was hitting. Then we checked that file and found it was crashing because of the wrongly encoded file. I am quite impressed.
Game changer
What do you like best about the product?
Finally, a way to debug those hard-to-reproduce setups. The UI is pretty and intuitive for the most part, and you feel like you're debugging from your IDE (and you actually can).
What do you dislike about the product?
Nested data structures and/or collections are sometimes harder to capture and it takes a few iterations to get to what you need. Also, conditions on breakpoints are somewhat limited.
What problems is the product solving and how is that benefiting you?
Identifying issues on a multi-tenant cloud-based application
Love using Rookout, for much faster than before production debugging on real time data
What do you like best about the product?
How fast it is to add a breakpoint and debug your production code, then add some kind of visibility and deploy it to production.
What do you dislike about the product?
The convenience of use, and the UX can still be improved.
It would be amazing if we could have the functionality of an IDE - searching for files, moving focus between tabs, keyboard shortcuts.
It would be amazing if we could have the functionality of an IDE - searching for files, moving focus between tabs, keyboard shortcuts.
What problems is the product solving and how is that benefiting you?
Rookout is helping me debug and find bugs a lot faster than having to write code and add metrics/logs so we can later debug and find the bug.
Fantastic Observability Platform; game changing impact
What do you like best about the product?
We were looking for a solution to help with a complex technology ecosystem and its fragmented observability tooling. Dynatrace has delivered exactly that - a solution that allows us to finally instrument our end-to-end customer journey across Serverless, Kubernetes and legacy technology platforms. It's dramatically reduced our MTTR by about 70% and allowed us to find issues in our applications that have impacted response times by 40% and have existed for years. It's become a core part of our development tooling.
What do you dislike about the product?
Dynatrace, as an expansive platform has quite a steep learning curve; this is particularly true in organizations where the observability mindset may not be mature. If I were to look to deploy Dynatrace to a new organization, I'd focus on the cultural elements of the transformation alongside the technological aspects.
What problems is the product solving and how is that benefiting you?
Dynatrace has helped us solve the end-to-end observability issue and introduce APM across all our applications, regardless of their base technology. It's become the glue that manages the health of our technology stacks and a vital insight into where engineering teams should be focussing their efforts.
One of the best observability tool.
What do you like best about the product?
Breadth coverage. Large tool integration coverage through Dynatrace Hub. Grail, Causal AI.
What do you dislike about the product?
Mainframe coverage, AS 400 Coverage, Batch Database coverage.
What problems is the product solving and how is that benefiting you?
It helped in fixing enormous false positive alerts from multiple observability solution by tools consolidation from 5 to 1.
Head of SRE
What do you like best about the product?
Goes really deep in to find to root cause with back traces. we have improved our applications performance in general and also helps us discover if any problem occurs/
What do you dislike about the product?
Environment management and licence management does not fully cover our needs. we use environments both for licence management concern and for clustering our services and etc.
What problems is the product solving and how is that benefiting you?
At the times of any attacks or outages it helps us see where does the problem starts. Also it helps us with our observability in one place at critical event times/
showing 31 - 40