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.
Useful for small things, less for serious debugging
What do you like best about the product?
Can easily set up and catch example data from runs. Can sometimes be a good alternative to going into the code and adding logs - doesn't require us to deploy and wait for logs to go live. UI is good and intuitive.
What do you dislike about the product?
When your flows contain a lot of data, and you want to explore all of this data, rookout doesn't catch all of it by default, and you are required to click "Collect more" which still doesn't collect all data you usually need if it's huge. I would prefer it to collect 1 example of full data from one flow/run instead of trying to collect partial samples from many flows. As a result rookout is mostly useless if you're trying to find, for example, if a specific entry exists in an array of size 100.
The most serious flaw is that conditional breakpoints a lot of times don't work (in Wix's case I never managed to create a conditional breakpoint by metaSiteId or requestId).
Also missing a feature to "collect sample from one run and that's it, stop".
The most serious flaw is that conditional breakpoints a lot of times don't work (in Wix's case I never managed to create a conditional breakpoint by metaSiteId or requestId).
Also missing a feature to "collect sample from one run and that's it, stop".
What problems is the product solving and how is that benefiting you?
Don't have to pollute code with logs. When debugging in production saves the time it takes for a log to deploy (and the time to write the log). As a result I'm writing less code that's not relaed to business logic.
- Leave a Comment |
- Mark review as helpful
Local environment level debugging on staging and production environments is awesome
What do you like best about the product?
Being able to diagnose bugs quickly without needing to mock data which produces the bug locally is a huge game changer. You can use the real data which is causing the error (with privacy filters) and place breakpoints to dig into what is going wrong without taking down environments. It's great!
What do you dislike about the product?
The main thing I would like to see is the ability to use rookout with client-side code, since that is where a lot of bugs originate with the modern complexity of front-end JavaScript frameworks.
What problems is the product solving and how is that benefiting you?
Rookout is helping us solve complex bugs that are difficult to reproduce or track down. It speeds up the time it takes to diagnose bugs by a huge margin by using non-breaking break points.
Amazing tool who helped me solve bugs in production a lot faster
What do you like best about the product?
It helps you debug in real time, catch complex issues and catch bugs that you didn't thought of when you first wrote the code and the tests.
What do you dislike about the product?
sometimes it slow, and you can't create conditions on keys in Map values.
What problems is the product solving and how is that benefiting you?
same as before - catch complex bugs by inspecting the values of the variables.
Seamless live debugging experience of huge monolith application system
What do you like best about the product?
This provides an easy and seamless experience of debugging live monolith application systems.
What do you dislike about the product?
Nothing to dislike as such, but if there were variable and attribute modification facilities while debugging, this could have been a great addition to it.
What problems is the product solving and how is that benefiting you?
This provides live debugging facilities for our big monolith application deployed on the cloud.
Great value - I'm excited to see what's next
What do you like best about the product?
It has slowly become the "go to" for debugging production issues.
I like that I can set it to notify me when a breakpoint is hit so I don't have to watch it always.
I like that I can set it to notify me when a breakpoint is hit so I don't have to watch it always.
What do you dislike about the product?
setup could be simpler
When I have to debug "large" objects it requires multiple rounds to do the "collect data" phase on specific objects, I would like to be able to predefine that so I don't have to go through everything again.
When I have to debug "large" objects it requires multiple rounds to do the "collect data" phase on specific objects, I would like to be able to predefine that so I don't have to go through everything again.
What problems is the product solving and how is that benefiting you?
It helps us see the process that the user is experiencing on the backend without having to deploy any new code or even contacting the user themselves
Debugging your code in production environment
What do you like best about the product?
The break point feature to debug your code in real time on real production environment
What do you dislike about the product?
The inteli plugging is very slow which I'm only using the web app
What problems is the product solving and how is that benefiting you?
Solving real time debugging till in production environments
Rookout became part of out arsenal when trying to debug and solve issues in production
What do you like best about the product?
The ability to quickly pinpoint issues in production without having to try and recreate the secnario in tests.
This allow us to add tests specificly to the issue and release a stable version.
This allow us to add tests specificly to the issue and release a stable version.
What do you dislike about the product?
We are working in Scala and we have a lot of implicit fields which are not shown and we need to specificly print them or extract them to be cought by rookout.
Also in case of heavy maps the need to go 1 by 1 to collect more data is annoying
Also in case of heavy maps the need to go 1 by 1 to collect more data is annoying
What problems is the product solving and how is that benefiting you?
It solves the problem of trying and recreate a bug in our testing env.
We can track an issue with our monitoring and see the bug in realtime in rookout.
This make the time from the report of an issue to the time of solving it quicker
We can track an issue with our monitoring and see the bug in realtime in rookout.
This make the time from the report of an issue to the time of solving it quicker
good product
What do you like best about the product?
it works great for the very basic usage of viewing flat fields of requests
What do you dislike about the product?
bad experience for filtering message, using of conditional breakpoints, viewing nested fields
What problems is the product solving and how is that benefiting you?
solve the need of push logs
Sadly bugs happens, rookout help us solve them in half the time.
What do you like best about the product?
The ability to debug production environment live easily and quickly.
What do you dislike about the product?
Need to add the ability to see the inline response of the line you selected.
What problems is the product solving and how is that benefiting you?
Checking the program state at a particular point in the production environment provides much data required to solve issues.
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.
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.
showing 41 - 50