Dynatrace Platform Subscription (DPS)
DynatraceExternal reviews
1,340 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Tried the product
What do you like best about the product?
the fact i could debug without the new to redeploy the system
What do you dislike about the product?
Had no support with ruby but they added it
What problems is the product solving and how is that benefiting you?
Issues with my code in production.
Easy way to debug production envs without breaking a keyboard while trying to reproduce incidents
What do you like best about the product?
Rookout provides a way to gain insights on distributed production environments and debug live on ongoing incidents - Making it a lot faster than understanding the issue by reproducing locally on your machine, struggling with humps of raw data from databases dumps and JSON files etc...
Conditional breakpoints and the ability to leave one running when setting a slack notification to be notified when the error re-occured is a game changer!
Conditional breakpoints and the ability to leave one running when setting a slack notification to be notified when the error re-occured is a game changer!
What do you dislike about the product?
Installation process could do with less friction - some languages/environments are troublesome to install (i.e. TypeScript)
UI is too simplistic and sometime confusing - more options and configuration options would be better
UI is too simplistic and sometime confusing - more options and configuration options would be better
What problems is the product solving and how is that benefiting you?
The biggest problem Rookout solves for me is reducing incidents' resolve time. When an issue occurs, and I don't understand why - setting a few breakpoints on Rookout most of the time provides an answer if you know what you are looking for.
Great solution for remote debugging
What do you like best about the product?
Easy to deploy, easy to use, great value.
What do you dislike about the product?
They release new versions all the time which makes it harder to keep up as a big slow company. We had to find a good stable version we like and to keep that.
What problems is the product solving and how is that benefiting you?
No need to release new versions to print more logs for debugging purposes on priduction environments. We give our customers solution to production issues much quicker.
Recommendations to others considering the product:
You have to try it to see the potential
Rookout saves us debugging time!
What do you like best about the product?
Rookout helps us debug production-only bugs much faster!
We have been using Rookout on thousands of production systems since late 2018. Instead of adding logging and waiting for a new build to roll out in a week, Rookout often shows us the problem so we can start on a fix immediately.
The Rookout team is very friendly, very bright, and very responsive to our requests. They are my favorite software vendor.
We have been using Rookout on thousands of production systems since late 2018. Instead of adding logging and waiting for a new build to roll out in a week, Rookout often shows us the problem so we can start on a fix immediately.
The Rookout team is very friendly, very bright, and very responsive to our requests. They are my favorite software vendor.
What do you dislike about the product?
Sometimes we wish we could see a little more context; for instance, it'd be nice to see the values of variables higher up in the stack.
What problems is the product solving and how is that benefiting you?
We're able to find and fix problems that we can't reproduce in staging. Although we strive not to be in that position, Rookout is a powerful tool when we find ourselves there.
A very useful for solution for certain situations
What do you like best about the product?
The ability to take a look at how my data is looking in real-time
What do you dislike about the product?
I cannot debug 2 services simultaneously from the same account
What problems is the product solving and how is that benefiting you?
Especially real-time production issues. We also leverage Rookout in our QA/test environment for when we need to understand complex flows.
I'm actively recommending Rookout to colleagues.
What do you like best about the product?
The ability to add non-breaking breakpoints in production systems, detecting bugs and recreating them in staging environment for fast solutions.
Especially, being able to trigger the team when the exception occur, instead of wasting time refreshing and watching for it to happen.
Being able to collect different objects and depth for analysis.
Especially, being able to trigger the team when the exception occur, instead of wasting time refreshing and watching for it to happen.
Being able to collect different objects and depth for analysis.
What do you dislike about the product?
I would like to see "dependent triggers" , activating 1 breakpoint only in case specific issue happend in other region.
For example, from within an exception handler, being able to collect data that happend before the exception.
For example, from within an exception handler, being able to collect data that happend before the exception.
What problems is the product solving and how is that benefiting you?
Online debugging, tracing of production issues with super-fast detection of the source of the issue
We've been able to reduce our bug-recreation times dramatically, solve issues that only occur in production without needing to create a very heavy testing scenarios.
We've been able to reduce our bug-recreation times dramatically, solve issues that only occur in production without needing to create a very heavy testing scenarios.
Rookout enables me to fetch and observe production in a very fast, fun, quick and breeze way.
What do you like best about the product?
* IDE-Like interface
* Integration to major source controls
* Integration to major source controls
What do you dislike about the product?
* The frontend can be slow when dealing with a vast amount of data.
What problems is the product solving and how is that benefiting you?
* Production debugging in a controlled environment.
Finally, a tool that let's me surgically debug in production
What do you like best about the product?
The ability to get the data I need, and ONLY the data I need from production, in an ad-hoc fashion. Extremely short feedback cycle.
What do you dislike about the product?
So far haven't found anything I dislike.
What problems is the product solving and how is that benefiting you?
Debugging issues in code running in production. Before Rookout I had to modify the code and re-deploy with extra logging, metrics etc. which was both a lengthy process and very expensive in terms of log storage and processing. Rookout also saved my developers the need to re-produce issues on their dev environments - we can just debug directly in production up to the point we have enough information to write a test.
Rookout provide an excellent tool for investigating bugs in production
What do you like best about the product?
I like best the base feature of being able to add observability to production systems without having to deploy that system.
What do you dislike about the product?
Price is a bit high for a product that I use relatively rarely (when there are production issues), but we understood it is worth it - because it brings the time it takes to investigate a production bug from hours to 20 minutes. (based on actual experience!)
What problems is the product solving and how is that benefiting you?
* Trying to investigate a bug in production without having to reproduce it locally.
* Easier to debug local containers, much faster than setting up an actual debugger.
* When there is an issue that happens rarely, we can add a monitor that will add log rows to logz.io, thereby allowing us to be alerted when the problem happens again a few days later.
* Easier to debug local containers, much faster than setting up an actual debugger.
* When there is an issue that happens rarely, we can add a monitor that will add log rows to logz.io, thereby allowing us to be alerted when the problem happens again a few days later.
Recommendations to others considering the product:
* Integrate with your backend systems by default, before the production bugs happen
* Provide as many details about the current environment as possible: project, container name, version, current user, etc. This will greatly improve the usability of Rookout and will enable more use cases.
* Provide as many details about the current environment as possible: project, container name, version, current user, etc. This will greatly improve the usability of Rookout and will enable more use cases.
A great tool with a very responsive team backing it up!
What do you like best about the product?
The product didn't support Ruby when we signed up, the Rookout team delivered us a Ruby agent within a few weeks of requesting one.
What do you dislike about the product?
We needed to upgrade to Ruby 2.6 to use the product. Other than that everything has been great.
What problems is the product solving and how is that benefiting you?
Quick diagnosis of issues in our production SaaS platform
showing 331 - 340