Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
A useful tool to enhance your debugging experience
What do you like best about the product?
The ease of integration to a new project is really great, from there the on boarding process is very simple
What do you dislike about the product?
The fact that it not possible to dynamically jump between execution points like in a real debugger
What problems is the product solving and how is that benefiting you?
Debugging sessions in production environment, on boarding of new peers to the codebase
- Leave a Comment |
- Mark review as helpful
Top 1 monitoring tool with world-class AI engine & effortless deployment.
What do you like best about the product?
AI-based anomaly detection, pure path technology for root cause analysis.
What do you dislike about the product?
Dashboarding can be improved & the cost is relatively high.
What problems is the product solving and how is that benefiting you?
Production issues in very fast-moving, dynamic & complex applications are straightforward to detect.
Rookout has really really helped us find lots and lots of bugs without making any changes to code
What do you like best about the product?
The way I can set breakpoints and get more info without making a single change
What do you dislike about the product?
I want to use rookout to measure time between points in an easy way
Also I want to be able to set things to happen in an exception is raised
Also I want to be able to set things to happen in an exception is raised
What problems is the product solving and how is that benefiting you?
Bugs bugs bugs.
Very helpful tool, highly recommended!
What do you like best about the product?
The conditions you can do on breakpoints
What do you dislike about the product?
You have to choose the specific source code that is currently running on your server
What problems is the product solving and how is that benefiting you?
Debugging issues on production environment
Best tool of its kind, cut our MTTR down by a lot when troubleshooting legacy code in prod!
What do you like best about the product?
We adopted Rookout at eagle.io because we were looking for a way to drive down the time to resolve customer support issues. We have a number of services running in prod,
and because we're a multi-tenant IoT platform there are soooo many places and soo many ways that something can go wrong.
Rookout has been an amazing supplement to Datadog (APM/logs/profiling etc). For example in the first week using rookout we had a prod incident, with Datadog we were able to narrow
down the problem to a certain block of code in a try catch block through inspecting traces and looking at correlated logs.
But we weren't logging the full error, and didn't have all the context we needed to pin down the exact problem. With Rookout, I set a few conditional non-breaking breakpoints,
validated that the problem was actually occurring where the logs seemed to indicate. I then browsed through the stack trace, saw the full error message, and all the local variables. Boom. Problem identified.
We wrote a unit test to cover the edge case, pushed it through our CI pipeline and out to prod.
Rather than having to redeploy to add more instrumentation, we solved the problem super quickly. That's the major value add. Without rookout, a problem that took us 15 minutes to identify and solve
could have blown out to a couple hours.
Also the rookout team is very helpful, super responsive, and enhances the product all the time. We asked them about a deeper datadog integration and a week or two later they had it in production.
I also compared this to Lightrun, which offers something similar, but found Rookout to be far easier to setup and use. Plus, Lightrun's nodejs support is just coming out as a beta feature, and we have some nodejs services.
and because we're a multi-tenant IoT platform there are soooo many places and soo many ways that something can go wrong.
Rookout has been an amazing supplement to Datadog (APM/logs/profiling etc). For example in the first week using rookout we had a prod incident, with Datadog we were able to narrow
down the problem to a certain block of code in a try catch block through inspecting traces and looking at correlated logs.
But we weren't logging the full error, and didn't have all the context we needed to pin down the exact problem. With Rookout, I set a few conditional non-breaking breakpoints,
validated that the problem was actually occurring where the logs seemed to indicate. I then browsed through the stack trace, saw the full error message, and all the local variables. Boom. Problem identified.
We wrote a unit test to cover the edge case, pushed it through our CI pipeline and out to prod.
Rather than having to redeploy to add more instrumentation, we solved the problem super quickly. That's the major value add. Without rookout, a problem that took us 15 minutes to identify and solve
could have blown out to a couple hours.
Also the rookout team is very helpful, super responsive, and enhances the product all the time. We asked them about a deeper datadog integration and a week or two later they had it in production.
I also compared this to Lightrun, which offers something similar, but found Rookout to be far easier to setup and use. Plus, Lightrun's nodejs support is just coming out as a beta feature, and we have some nodejs services.
What do you dislike about the product?
The web UI could have a few more power user shortcuts.
The product is still relatively new compared to things like datadog, so expect a few minor things to crop up. Eg we were unable to rename a log target after creating it, but as soon as we pointed that out, the team implemented that feature very quickly.
The product is still relatively new compared to things like datadog, so expect a few minor things to crop up. Eg we were unable to rename a log target after creating it, but as soon as we pointed that out, the team implemented that feature very quickly.
What problems is the product solving and how is that benefiting you?
Faster time to diagnosing issues without deploying new instrumentation code. Ability to log less in production and save on costs for the "just in case" logs that ended up driving a lot of log volume.
This has been really helpful as we modernise a few older services and refactor parts of the codebase that weren't as well tested as the newer code that we write these days.
This has been really helpful as we modernise a few older services and refactor parts of the codebase that weren't as well tested as the newer code that we write these days.
Recommendations to others considering the product:
Play around with it. It's one of those things that seems like it could be useful, but you ask yourself if it's just a cool new thing. We've found it super useful for operations/debugging across services.
It definitely has a place as part of your observability/ops stack.
It definitely has a place as part of your observability/ops stack.
Very useful and original!
What do you like best about the product?
It provides a way to do something I had never considered possible; debugging code while it's live in production, setting breakpoints that capture actual live data.
What do you dislike about the product?
There is a steepish initial learning curve, but small price to pay for the almost magical benefits.
What problems is the product solving and how is that benefiting you?
Identifiying bugs that only manifested in a prod environment with specific user data; the types of problems that are very hard to replicate in a local testing environment. The benefit is the time saved trying to replicate a very particular set of circumstances to trap a bug.
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.
showing 201 - 210