External reviews
1,344 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Dynatrace Review
What do you like best about the product?
APM Functonlity and pure path function of Dynatrace
What do you dislike about the product?
Sometimes it get confusing for selecting the server matrics for multiple server in one graph.
What problems is the product solving and how is that benefiting you?
Mostly we used Dynatrace for Application Performance Monitoring.
Recommendations to others considering the product:
Best tool inarket for APM
Solid monitoring with dynatrace
What do you like best about the product?
It has realtime monitoring for performance
What do you dislike about the product?
Documentation needs to be improve as well as dashboard
What problems is the product solving and how is that benefiting you?
It can be used for different scenarios as well as it gives the detailed analysis for profiling
Dynatrace is very good morning tool
What do you like best about the product?
Dynatrace is most helpful for checking the pure paths and problems.
What do you dislike about the product?
Can not create few customized dashboard which consider as less priority.
What problems is the product solving and how is that benefiting you?
Performance of the application and environment monitoring
Time saver when we want to debug Production and UAT environment Orders
What do you like best about the product?
1. We need not trigger Production in the local environment, which takes a huge time. Instead, we can use Rookout to debug.
2.Time save when we want to check the NPE issues using Rookout.
3. We can also see the nested JSON payload data.
4. Performance issue reduced in this upgraded version
2.Time save when we want to check the NPE issues using Rookout.
3. We can also see the nested JSON payload data.
4. Performance issue reduced in this upgraded version
What do you dislike about the product?
1. We do not have a Perforce option for the branch code selection. We just have Git.
2. If can have the option to give parameters from the UI to integrate the Rook out with Environment
2. If can have the option to give parameters from the UI to integrate the Rook out with Environment
What problems is the product solving and how is that benefiting you?
1. We need not trigger Production in the local environment, which takes a huge time. Instead, we can use Rookout to debug.
2.Time save when we want to check the NPE issues using Rookout.
3. We can also see the nested JSON payload data.
4. Performance issue reduced in this upgraded version
2.Time save when we want to check the NPE issues using Rookout.
3. We can also see the nested JSON payload data.
4. Performance issue reduced in this upgraded version
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
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.
showing 301 - 310