Dynatrace (Contracts)
DynatraceExternal reviews
1,344 reviews
from
and
External reviews are not included in the AWS star rating for the product.
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.
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.
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.
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.
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.
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
Rookout has saved me valuable amounts of time
What do you like best about the product?
Orders of magnitude speed up to debugging times
What do you dislike about the product?
The UI and interaction has changed a lot, so I have had to relearn the tool over time
What problems is the product solving and how is that benefiting you?
Fixing bugs in distributed applications in a fraction of the time it used to take.
Dynatrace is now a fantastic network security tool
What do you like best about the product?
The product offers a valuable insight into IT processes and monitors numerous bottlenecks in infrastructure efficiency. With infrastructure and network visibility, the company prioritizes capital investment and focuses on areas with urgent needs. A robust dashboard built as a single glass panel gives reliable and real-time data on performance problems.
What do you dislike about the product?
Often the warnings may be a little too big or need some adaptability to the individual organisation's needs, because there is no universal size for everyone. The lack of familiarity with the product will prove a sticking point without a guide specialist. Assimilation doesn't always go smooth, requiring further education and understanding to step forward.
What problems is the product solving and how is that benefiting you?
Dynatrace offers real-time monitoring that provides key visibility in consistently low areas and optimizes infrastructure usage. Ability to recognise productivity problems and areas for change. The screen and the glass pane provide key information and indicators to set a benchmark and any user spike can be monitored and a particular cause or rise in prices can be linked to it.
Recommendations to others considering the product:
Ideally, complete monitoring criteria are understood before delivery. Start with the collection of requirements, the delivery scope and the timeline to deploy globally. The key emphasis will be on context of service convergence that problems are automatically raised as just a fare.
Control of industrial design
What do you like best about the product?
A semen quality into IT processes and a variety of bottlenecks in services are monitored. The network and technology visibility helps the company to prioritize capital investment and concentrate on urgent needs areas. With an integrated dashboard built as a single glass panel, accurate and real productivity data are provided.
What do you dislike about the product?
Often warnings may become a little too large and require some practice, because there is no standard size for all. There can be no expertise in using the product without the help of a professional. At present, incorporation does not go perfectly and needs more learning and testing to step on.
What problems is the product solving and how is that benefiting you?
Dynatrace offers real-time tracking for low performance areas and optimizes the use of infrastructure. Capacity to recognise problems with results and areas to be improved. The monitor and golden goblet panel provide important data and indicators that help to define a baseline and any consumption spike can be monitored and assigned to a particular trigger or demand growth.
Recommendations to others considering the product:
Until deployment, complete monitoring criteria are ideally understood. Start with the collection of specifications, the deployment scene and the timeline for intending. Main focus will be the areas of data sharing now and BMC Coil so insure that any problems are immediately raised as a fare.
showing 141 - 150