Dynatrace (Contracts)
DynatraceExternal reviews
1,344 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Rookout Rocks!
What do you like best about the product?
Once installed, quick and easy to set up and get debugging going across all our servers.
What do you dislike about the product?
Nothing at all - I am super happy with Rookout.
What problems is the product solving and how is that benefiting you?
For those one-of-a-kind, real-time, needle-in-a-haystack bugs, Rookout is the go-to tool in my bag. Many of our customers have unique issues that would be very difficult to find the root cause if it weren't for Rookout.
Recommendations to others considering the product:
What are you waiting for?!?
Crazy useful new tool in the toolbox
What do you like best about the product?
Rookout is in a class of its own -- literally. It defies categorization in the normal observability or dev tools ecosystem. What I love about it is that I can do things I can't do elsewhere.
Specifically, I can drop into my runtime application and set probes that let me observe behavior that I wouldn't otherwise have visibility into due to a lack of details in my logs, metrics, and tracing. It's the closest thing to the experience a developer gets when debugging locally in their IDE.
Over the last year, we've had several production issues and weird bug reports from customers that left us scratching our heads initially. But with Rookout, we were able to drop into a few parts of our code and effectively add some log statements (scoped narrowly to the situation/customer) and quickly figure out the problem.
Specifically, I can drop into my runtime application and set probes that let me observe behavior that I wouldn't otherwise have visibility into due to a lack of details in my logs, metrics, and tracing. It's the closest thing to the experience a developer gets when debugging locally in their IDE.
Over the last year, we've had several production issues and weird bug reports from customers that left us scratching our heads initially. But with Rookout, we were able to drop into a few parts of our code and effectively add some log statements (scoped narrowly to the situation/customer) and quickly figure out the problem.
What do you dislike about the product?
I have two issues with Rookout... one practical and one meta.
The practical issue is that we occasionally find ourselves at a roadblock because our tech stack/code is incompatible with the Rookout agent. Specifically, the problem manifests itself in the form of a "breakpoint" that can't be set. Fortunately, when we open a ticket with their support team they often are 1-2 steps ahead of us and usually have a new build of the Rookout agent to try out, resolving the problem.
The meta issue is a bit trickier: due to the nature of the solution, it's not a thing we use daily. As a result, it hasn't ingrained itself each of our team member's workflows. So we've had a few situations where we didn't think to use Rookout at first. What they do is something that wasn't really possible and so we're fighting with 10-20 years of experience that our developers have built up, assuming that dropping into an application's runtime and inspecting specific lines of code wasn't really possible.
The practical issue is that we occasionally find ourselves at a roadblock because our tech stack/code is incompatible with the Rookout agent. Specifically, the problem manifests itself in the form of a "breakpoint" that can't be set. Fortunately, when we open a ticket with their support team they often are 1-2 steps ahead of us and usually have a new build of the Rookout agent to try out, resolving the problem.
The meta issue is a bit trickier: due to the nature of the solution, it's not a thing we use daily. As a result, it hasn't ingrained itself each of our team member's workflows. So we've had a few situations where we didn't think to use Rookout at first. What they do is something that wasn't really possible and so we're fighting with 10-20 years of experience that our developers have built up, assuming that dropping into an application's runtime and inspecting specific lines of code wasn't really possible.
What problems is the product solving and how is that benefiting you?
More quickly identify the root cause of problems that we couldn't otherwise resolve using our existing metrics, logs, and traces.
Game changer in your TTM.
What do you like best about the product?
An ability to debug by ongoing and independently the environment which is not under your responsabilty on one hand while on another you don't need to try and recreate the issue on your own development environment, which is usually different.
What do you dislike about the product?
The advantages of the tool are covering all the dissadvantes.
What problems is the product solving and how is that benefiting you?
Defects/Bugs identied by external testing teams on ENVs installed on clients servers.
Easy and useful experience
What do you like best about the product?
The product is easy to use.
Make debugging simple when working with multiple environments.
Make debugging simple when working with multiple environments.
What do you dislike about the product?
Rookout does not have front-end support.
What problems is the product solving and how is that benefiting you?
- Dubug production environments and modern architectures, such as Kubernetes deployments and serverless.
- Gain a deep level of observability into our application, and therefore an understanding of what’s happening in it, also while it’s running. We’re able to do this without adding loglines metrics or reproducing your bug.
- Gain a deep level of observability into our application, and therefore an understanding of what’s happening in it, also while it’s running. We’re able to do this without adding loglines metrics or reproducing your bug.
Debug microservices like they run on your local machine
What do you like best about the product?
With Rookout I don't need to reproduce deployments and environments, which saves me a lot of time and effort that I am able to invest in other tasks, such as building new features.
What do you dislike about the product?
Nothing. I’ve been using Rookout for a while now and am perfectly happy with it.
What problems is the product solving and how is that benefiting you?
I solve bugs raised by QA and able to see exactly how the service behaves by adding breakpoints at the QA environments, like hooking a debugger without the risk of stuck instances
Recommendations to others considering the product:
If you work with microservices, you got to use this tool
Rookout is our eyes into production
What do you like best about the product?
Rookout enables us to get a clear understanding of our flows/bugs in production. We can instantly add logs, measure latencies, and debug our production flows without the need for tedious cycles to reproduce production issues in our test environment.
It's an essential tool in our production arsenal and saves a lot of time and effort supporting the service.
It also makes the team members; life better.
It's an essential tool in our production arsenal and saves a lot of time and effort supporting the service.
It also makes the team members; life better.
What do you dislike about the product?
UI/UX can and should be improved to mimic IDE behavior better.
There are still some bugs, mainly around UI
There are still some bugs, mainly around UI
What problems is the product solving and how is that benefiting you?
With Rookout, we can:
1. Debug issues on production without the need to reproduce on our test env.
2. Use the stack trace of the Rookout breakpoint to understand the software abstraction in real-time (like which implementation is running).
3. Use the profiling capabilities (time measures, rate, etc.) to find latency hotspots of specific flows (with conditional breakpoint).
4. Understand distributed flows (like un-even processing of Kafka partitions etc.).
1. Debug issues on production without the need to reproduce on our test env.
2. Use the stack trace of the Rookout breakpoint to understand the software abstraction in real-time (like which implementation is running).
3. Use the profiling capabilities (time measures, rate, etc.) to find latency hotspots of specific flows (with conditional breakpoint).
4. Understand distributed flows (like un-even processing of Kafka partitions etc.).
Used Rookout as a tool for real time debugging
What do you like best about the product?
- Being able to debug code in production in real time - big advantage!!
- Rookout supports a wide range of technologies
- Being able to change logs and metrics sent from production dynamically.
- Rookout supports a wide range of technologies
- Being able to change logs and metrics sent from production dynamically.
What do you dislike about the product?
The tool can be helpful for a very specific range of problems, hence it's sometimes easier to debug using existing tools or dashboards that cover a wider range of problems.
The need to configure Rookout on every component is not very scalable.
The need to configure Rookout on every component is not very scalable.
What problems is the product solving and how is that benefiting you?
Debugging production in real time, configuring logs dynamically.
Rookout is an amazing tool that saves us a lot of time!
What do you like best about the product?
Rookout enables our team to debug our complex production services without the need to change the code. It saves us hours of developers and other supporting teams time, time that was, in the past, spent on adding traces in the code and deploying a new version to production. With Rookout we just set a break point in our code and can see, in seconds, the variables and call stack with ease.
With Rookout we can reduce the effort to reproduce deployments and environments, which saves us a
lot of time and effort that we are able to invest in other tasks, such as building new features.
Their support is amazing and they are very open for suggestions on how to improve the product.
With Rookout we can reduce the effort to reproduce deployments and environments, which saves us a
lot of time and effort that we are able to invest in other tasks, such as building new features.
Their support is amazing and they are very open for suggestions on how to improve the product.
What do you dislike about the product?
Nothing. I’ve been using Rookout for a while now and am perfectly happy with it.
What problems is the product solving and how is that benefiting you?
We are using Rookout to debug customers' issues in our many production services in hundreds of servers.
With ease with can set a break point and review the state of the code in a specific scenario.
With ease with can set a break point and review the state of the code in a specific scenario.
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.
showing 311 - 320