Easily debug tool to use over production and development environment
What do you like best about the product?
It is very simple to use, allow you to debug the code easily.
What do you dislike about the product?
The search on the rookout web is not the best - need to search by the name of the class and it offers you all the existing repositories which is a bit confusing (you can see the repo name on the side of the class name, and it can be missed so the debug point are not aligned with the real code lines)
better to have more clear class name to repo relation to avoid confusion.
also, when you want to put multiple break points in one flow that contains multiple classes - need to xearch by class name each one. If it could be like on intelij - command + click on the function name and it will lead you to the relevant class - it can improve the ux a lot.
What problems is the product solving and how is that benefiting you?
debug bugs on production live environment without change/do anything.
Offers a wide range of functionalities and excellent support
What is our primary use case?
Dynatrace is a strategic application performance monitoring tool. We use it for every use case related to monitoring applications. We use the SaaS solution to monitor on-premises.
We also use Dynatrace for monitoring third-party applications and our own applications.
What is most valuable?
Dynatrace has the most features compared to other products we looked at. However, the best thing, in my opinion, is the support from the Dynatrace team. They provide a success manager and a team of engineers who are quick to answer questions and provide help. They even assign architects and engineers to ensure our productivity with the tool.
What needs improvement?
Dynatrace is a complicated tool that requires time and investment to fully understand. It's not something you can simply turn on and use. You need a dedicated team to use it.
So, the only challenge is that it's an extensive tool that requires a significant amount of time to learn.
Moreover, Dynatrace delivers new functionality every month. They have a space on their website where you can request new features, and they actively monitor it. They provide feedback and ask questions about the requested features. Suddenly, those features appear in the product. Dynatrace is really good at incorporating user suggestions. So, there's nothing that I want to add that they haven't already considered.
For how long have I used the solution?
I've been using Dynatrace for about three to four years. We are using the latest version since it's a SaaS solution. It's always up to date.
What do I think about the stability of the solution?
Dynatrace has been very stable without any issues. I would rate the stability a solid ten.
What do I think about the scalability of the solution?
Dynatrace is massively scalable. I would rate the scalability a ten out of ten.
We have around 200 users using this solution in our organization.
How are customer service and support?
The support has been exceptional.
How would you rate customer service and support?
How was the initial setup?
The initial setup is actually really easy to install. It's a quick process. You can turn it on and load the SaaS Dynatrace solution in just five minutes.
However, there is additional configuration and tweaking that may take years to optimize fully. The interface configuration is not easy; given the tool's complexity, it requires time to become familiar with it.
There is maintenance involved. Dynatrace releases patches every two to four weeks. The only painful part there is the agents we run on-prem and on our servers, it needs the agent the application needs to restart.
So, sometimes you delay the update to minimize disruption but the patches are sent to us every month.
What's my experience with pricing, setup cost, and licensing?
Dynatrace is expensive, but it offers good value for the money. I would rate the pricing a seven out of ten, with one being cheap, and ten being expensive. It is not cheap; it could always be cheaper.
The license has recently changed to a yearly subscription model. So, it's an annual subscription. We pay even more to have an engineer as part of our team for two days a week. It incurs an additional cost.
What other advice do I have?
I would say to go for it. You won't regret it. Dynatrace has been an awesome product. The complexity of Dynatrace arises from its vast array of features and settings. It takes a considerable amount of time to learn and understand all the options it offers.
Overall, I would rate the solution a ten out of ten.
Debug on the fly
What do you like best about the product?
ability to set breakpoints and get variable details
What do you dislike about the product?
ability to execute in line commands for basic function call or variable calculations
What problems is the product solving and how is that benefiting you?
I don't need to worry about replicating the issue in my local systems anymore
Dynatrace platform
What do you like best about the product?
The most AI technoloy and cloud platoform is present like monitoring, problem alerts, createing dashboards, analysing the root cause of the issues , integration of the applications many more.
What do you dislike about the product?
No dislike at present but it is very useful in all aspects, like keeping in maintenance, real user monitoring to monitor, once one agent installed all will detect automatically.
What problems is the product solving and how is that benefiting you?
Synthetic monitoring, log monitoring, Application performance monitoring, alert monitoring, maintenance windows, Real user monitoring, one agent installation to capture automatically this are all solutions to solve the issues
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.
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
