Sign in Agent Mode
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Dynatrace Classic

Dynatrace

Reviews from AWS customer

10 AWS reviews

External reviews

1,345 reviews
from and

External reviews are not included in the AWS star rating for the product.


    Lokesha K.

AI-Driven Observability with Clear Root-Cause Insights and Easy Onboarding

  • January 16, 2026
  • Review provided by G2

What do you like best about the product?
Dynatrace provides deep, AI-driven monitoring and observability across hybrid and multi-cloud environments, with excellent end-to-end visibility. Its AI engine automatically detects anomalies, reduces noise, and delivers clear root-cause insights. The Dynatrace interface is clean, the topology mapping is incredibly accurate, and the single-agent deployment makes onboarding very easy.
What do you dislike about the product?
Dynatrace’s pricing model can become expensive as environments scale, especially for organizations with large Kubernetes or microservices deployments. Integration with some ITSM tools also requires additional configuration effort.
What problems is the product solving and how is that benefiting you?
Dynatrace helps us achieve real-time observability across our infrastructure and cloud workloads. With AI providing automatic RCA, our MTTR has been reduced significantly. We’re also able to proactively detect performance degradation before end users are impacted.


    Pankaj B.

The #1 Observability Tool for Implementing and Monitoring Applications

  • January 13, 2026
  • Review provided by G2

What do you like best about the product?
Dynatrace is one of the powerful observability and infrastructure monitoring tools. It expands its capabilities with APM, DEM, and infra monitoring, along with support for databases and multiple cloud platforms. I use it daily to monitor applications and our cloud stack.

It has wide integration support with third-party tools, so we can integrate and monitor almost everything in Dynatrace. They also provide active customer support, helping us when we get stuck and resolving our problems and issues.

We can monitor our application’s golden metrics, such as logs, metrics, traces, and events, along with CPU, memory, disk, and other infrastructure metrics. Overall, it’s one of the best and most user-friendly tools to monitor and secure our applications.
What do you dislike about the product?
There’s nothing to dislike. It’s the number 1 observability tool to use, implement, and monitor applications.
What problems is the product solving and how is that benefiting you?
In Dynatrace, we can set up alerts based on anomalies as well as static thresholds. It can notify you before your application goes down, or when any issue occurs, helping you keep things secure. We can also set service-level boundaries for SLA, SLO, and SLI. In addition, we can create multiple dashboards for the DevOps team to keep an eye on the application’s performance. Overall, it helps you secure your application and address problems before it goes down.


    Vaibhav Karad

AI-driven monitoring has reduced incident resolution times and improves release confidence

  • January 13, 2026
  • Review from a verified AWS customer

What is our primary use case?

My main use case for Dynatrace involves daily work with monitoring charts, setting up alerts, and tracking response times and error rates to identify slow transaction bottlenecks in microservices. I also manage infrastructure monitoring, such as CPU, memory, and disk issues. When anomalies in resource consumption arise, I utilize the AI-powered Dynatrace Davis engine to quickly identify the root cause. Additionally, we employ real user monitoring (RUM) for alert and incident management, creating alerts with tools such as PagerDuty and ServiceNow when we need to raise incidents. We also focus on observability in our workloads deployed on a Kubernetes environment, including microservices and various servers.

I have a specific example of how Dynatrace helped me solve performance issues, particularly with slow response times in payment services, which could reach eight to ten seconds. I had to check the trace routes and flow to understand these delays during calls to external APIs, where I discovered that third-party API calls were waiting for responses due to DNS resolution issues. Dynatrace identified this slowdown, correlating it with spikes in DNS lookup times in a node in our Kubernetes cluster. After we handled deployment releases, we dropped response times to under one second. This solution significantly improved our common problems, achieving a success rate of almost fifty percent in troubleshooting.

How has it helped my organization?

Dynatrace has positively impacted my organization by reducing incident resolution times, with Davis AI helping to pinpoint root causes effectively. We have seen a reduction of thirty to sixty percent in mean time to resolution (MTTR) for prioritized incidents and fewer escalations. Additionally, Dynatrace has helped us reduce alert noise, leading to forty to seventy percent fewer alerts while routing incidents more reliably to the correct teams. The quality of our releases improves gradually due to automated validation, allowing for quicker rollbacks and issue detection within minutes of deployment, which increases confidence in our CI/CD processes.

Dynatrace has contributed to significant improvements such as reducing P1 tickets resolution time from four hours to under one hour and drastically cutting alert volumes from between two hundred to four hundred alerts per week down to approximately sixty to one hundred twenty. The latency for reporting ticket issues dropped with PurePath and RUM data, improving from over three point five seconds to around two point one seconds. We also recorded substantial reductions in both latency from three point eight to one point four seconds and error rates averaging under one percent after implementing the findings from Dynatrace analytics.

What is most valuable?

The best features that Dynatrace offers include the AI-powered root cause analysis with Davis AI, which automatically identifies root causes by correlating metrics, logs, and traces, saving substantial time during incident resolution. Full-stack observability is another top feature, as it covers application, infrastructure, and network-related services while integrating with cloud environments. I appreciate the PurePath distributed tracing that provides deep dive insights into every transaction across microservices, helping us pinpoint slow database queries and external API calls. RUM allows us to track actual user sessions that impact UX, while synthetic monitoring proactively detects issues before they affect real users. OneAgents simplify infrastructure-related configurations, and I want to emphasize the importance of business analytics integration to tie technical metrics with business KPIs, as my role involves prioritizing issues based on their impact on business outcomes.

The feature that saves me the most time is Davis AI, as it automatically analyzes all data elements, understands metrics, logs, and traces, and pinpoints exact root causes of issues. Instead of manually digging through dashboards, I receive clear explanations of problems, such as high CPU usage due to garbage collection or memory issues, which drastically reduce the mean time to resolution (MTTR). The manual investigations that used to take hours can now be solved in under a minute, eliminating guesswork and allowing me to respond quickly without needing cross-team checks. For instance, Davis AI recently flagged a slowdown in microservices that led me to a recent inefficient data query introduced during deployment, allowing me to roll back changes in only fifteen minutes.

What needs improvement?

Beyond the features already discussed, I would like to see improvements in auto-discovery, smart instrumentation, and a unified data model to centralize all metrics and events on a single platform. This change would minimize the need to jump between tools and manually stitch data together. Continuous improvement features tied to SLO objectives should also ensure deployments meet performance standards.

In terms of improvements, I believe Dynatrace could enhance cost and licensing structures, as the current pricing can be expensive for large-scale deployments. More flexible and granular billing options would be beneficial, especially for ephemeral workloads. Additionally, while the initial setup is straightforward, understanding advanced features requires expertise. Improvements in user guidance, such as tutorials or workflow documentation, could help new users navigate the platform more easily, particularly with customization options and dashboard enhancements.

Further improvements could include fostering deep native integrations with major platforms and enhancing the ease of integrating with CI/CD tools such as Jenkins or GitHub Actions. Additionally, supporting better OpenTelemetry for custom traces and metrics would simplify setups. Native integrations with BI tools would enhance our analytical capabilities, making real-time dashboard creation easier.

For how long have I used the solution?

I have been using Dynatrace for three years, having initially been introduced to Kibana and other solutions such as AWS Watch before that.

How was the initial setup?

Dynatrace was purchased through the AWS Marketplace, which made the setup process straightforward; however, I believe no additional improvements are necessary beyond what I have already mentioned.

What other advice do I have?

For others exploring Dynatrace, my advice is to start by defining clear goals, such as improving incident resolution times or release quality. Familiarizing oneself with key features such as Davis AI and ensuring thorough tagging of services is essential for cleaner dashboards. Utilize AI for problem detection and integrate Dynatrace with incident management tools for efficient workflows.

Before concluding, I want to emphasize the importance of leveraging advanced features beyond basic monitoring, particularly with SLOs and release validations, and to be mindful of budgeting, as Dynatrace can get expensive at scale. I would rate this product an eight out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?


    Retail

Overly Complex with Misleading Dashboards and False Positives

  • January 07, 2026
  • Review provided by G2

What do you like best about the product?
three years ago we were early adopters and it was brilliant.
What do you dislike about the product?
it became too complicated and gave too many false positives. Dashboards are inaccurate and misleading.
What problems is the product solving and how is that benefiting you?
initially helped identify root cause on tricky issues with application and aws platform


    Vinothkumar Sugumar

Unified dashboards have provided end-to-end visibility and now streamline API latency troubleshooting

  • December 30, 2025
  • Review provided by PeerSpot

What is our primary use case?

My main use case for Dynatrace is logs and tracking metrics, mostly API latencies, to find API latency metrics and monitor whole services and microservices.

About my main use case with Dynatrace, I will add a few things: first is that we create a custom dashboard, which is very helpful for us to monitor multiple microservices, since the application relies on multiple services. Then we have a few features including error detection, such as how many 4xx error rates are coming, what 5xx error rates are coming, and what are the client-side and server-side problems. Those kinds of built-in Dynatrace alert systems we can use for latency and error classification. We can link those things into channels such as Slack, email, or mostly PagerDuty, so the on-call person will receive these alerts.

What is most valuable?

The best features Dynatrace offers include AI-based metrics collection, which impresses me a lot because it is very helpful to quickly check all the issues that come up. The first thing is end-to-end visibility across all the services. That is one thing where we can know the infrastructures, hosts, containers, VMs, and what is happening with the application. Then this automatic discovery and mapping helps a lot. Distributed tracing, which is the PurePath thing, is a very helpful feature. For root cause analysis, the recent Davis AI is something game-changing and is helping a lot, saving a lot of time. That is the main feature right now. The remaining things are the foundational features and making access to all the features so quick. Davis AI makes use of the features that exist, and now I am using those features. So that is a good thing.

The root cause analysis feature specifically helps my team save time or solve issues by providing detailed timings and external APIs and cache whenever the PurePath thing comes, to trace every subsequent call. We are not only working with our own microservices; we are working along with multiple vendors. Sometimes the latency is not from our system but from a vendor system. During those times, we see why this service is taking a lot of time because this service is waiting for a call. These small details on timings and the DB cache add so much value to the PurePath thing. The AI powered Davis detects anomalies and root cause issues across the stack, which is also a valuable feature. Application topology and network flows are also very helpful. These things are primarily helping us.

Before moving on, I would appreciate the custom dashboard and visualization part of Dynatrace, where I did not talk much about those things. The real-time charts are very helpful to monitor the health of the application. Heat maps are really cool to see, and service flow maps are really required to understand the things. The key performance indicators are very good. These are the key standpoints of my application metrics. Whenever I am the on-call person in PagerDuty, these are the things I am fundamentally looking for. This is a lookup book for me to make sure this application is in good health.

Dynatrace has positively impacted my organization by allowing us to see very quick action whenever there is an issue with production. We can quickly open the dashboard, see the error rates where it is happening, and perform a quick analysis to find the root cause. That is a huge part. The second part is improvisation; whenever we come to a stable state and have some technical debt to take, we can check what APIs are causing latency and work on those issues, asking why it is happening. Sometimes it leads to redesigning the domain, coming from the dashboards. Every time we do not know how many services exist or why a particular service is working for this domain while we are in some centralized stage. But while coming to this Dynatrace dashboard, seeing all services in one place helps us think why this service is talking to this service. We can classify domain-level and regroup the domain. This way, it is helping us by giving a mental model and a mental map to track everything. That is a huge win for us.

What needs improvement?

I think Dynatrace can be improved in dashboard creation, as this is the face of a product. Although Dynatrace may have many things, new users typically do not know the whole power of the product. To onboard new people, it would be beneficial to provide template dashboards or suggested dashboards. Organizations working with microservice architecture will follow some templates, so suggesting simple, hand-picked features that are really helpful could make a difference. Quick configurable and customizable templates would be very useful. Whenever they come into the product, they can use this template and feel that their product is applied to it. Immediately, they will think everything is online and can improve easily. This base can be provided in template form. Since Dynatrace has a lot of features now, the AI integration makes it simple, but the product itself is very huge. To understand and utilize it, maybe it would be good to index the essential features.

For how long have I used the solution?

I have been using Dynatrace for three years.

What do I think about the stability of the solution?

Dynatrace is stable.

What do I think about the scalability of the solution?

Dynatrace's scalability is very good.

How are customer service and support?

The customer support for Dynatrace is good.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Previously, we used Grafana as a different solution. We switched because Dynatrace provides better overall metrics, but switching the solution is not my decision; it is an organization-wide decision, so I do not have much influence there or comment on it.

What was our ROI?

There is definitely a return on investment; I see time saving. Also, the employees working with operations do not require that level anymore, so we can reduce a few.

What's my experience with pricing, setup cost, and licensing?

My experience with pricing, setup cost, and licensing indicates that it is a bit pricey, but it is very much worth it. We can maintain licenses as a product that we must own because this is an alerting system and metric system. The product I am working with is critical, having millions of users coming and going; it is the health monitor part of that product. It is essential, and it is okay to spend that money.

Which other solutions did I evaluate?

Before choosing Dynatrace, we evaluated Grafana, and we considered moving from Grafana to Dynatrace because of specific benefits. We had our own trade-offs, and ultimately, we chose Dynatrace.

What other advice do I have?

I would advise others looking into using Dynatrace to set up as many metrics for the product they are using as possible, and I ask them to create dashboards to monitor.

Overall, Dynatrace is a good product; I will definitely suggest it. It offers strong usage while addressing production issues and health monitoring. It is a very good product. I rate this product an eight out of ten.


    BasilJiji

Unified observability has improved incident response and transforms complexity into insight

  • December 29, 2025
  • Review from a verified AWS customer

What is our primary use case?

My primary focus is unified observability and security, and in my organization, we use Dynatrace for monitoring the infrastructure, cloud platforms, and application performance to reduce major outages and intelligently combine metrics, logs, and traces into a single view.

We use Dynatrace's OneAgent to automatically discover and instrument our entire stack from the front-end user interaction to the back-end database. During high traffic events, we monitor real-time response and use this AI to automatically pinpoint the root cause of any slowdowns before they impact the customers.

What is most valuable?

Dynatrace is a super platform that easily manages over 10,000 hosts and is highly stable, making it the best.

Dynatrace manages over that many hosts through an elastic grid architecture, which efficiently handles thousands of services and containers with minimal overhead.

Dynatrace has drastically improved our MTTR and provides one monitoring tool across the entire landscape. We have achieved a massive reduction in operational costs and tool sprawl.

We have seen an average three-year return on investment of 451%, which is a huge number when it comes to the saving part. We are seeing an increase in the efficiency for our IT and DevOps team with introducing Dynatrace, including 40% fewer Sev1 and Sev2 outages annually.

Dynatrace is a powerful expert-level tool that transforms complexity into a business asset. The inclusion of runtime application security has become a critical feature for our modern DevSecOps workflows.

What needs improvement?

The platform could improve its custom visualization options, as some executive dashboards feel restrictive compared to other tools. Additionally, making raw log data more cost-effective would add significant value.

For how long have I used the solution?

I have been using Dynatrace since early 2022 to manage our centralized log management and observability initiatives across multiple large-scale environments.

What do I think about the stability of the solution?

Dynatrace is very stable, with most users rating its reliability between an 8 and 10 on a 10-point scale, featuring an always-on architecture designed to be as resilient as the systems it monitors.

What do I think about the scalability of the solution?

Dynatrace is built for hyper-scale, easily managing over a lot of hosts through an elastic grid architecture. It also efficiently handles thousands of services and containers.

How are customer service and support?

Technical support is highly responsive and expert, with users particularly valuing the Guardian Program for hands-on assistance during critical issues.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We previously used a mix of traditional monitoring tools such as SolarWinds and Splunk, but we switched because we needed a more unified platform that was easier to deploy and provided better business-level visibility.

How was the initial setup?

Purchasing Dynatrace through the AWS Marketplace was straightforward and allowed us to leverage our existing AWS spend. While the cost can be high for CPU-intensive tasks, the automated setup and tools consolidation save us significant money.

What about the implementation team?

I advise defining a goal tagging policy before rolling it out to ensure your data stays organized as you scale. Also, start with a 15-day free trial to test OneAgent on your own machines and see automatic discovery in action.

What was our ROI?

We have seen an average three-year return on investment of 451%. Key metrics include 40% fewer Sev1 and Sev2 outages annually along with a 37% increase in the efficiency for our IT and DevOps team.

Which other solutions did I evaluate?

We evaluated several competitors, including New Relic, DataDog, and AppDynamics, but we ultimately chose Dynatrace for its superior automation, security-conscious design, and advanced AI-powered root cause analysis.

What other advice do I have?

I would rate this product a 9 out of 10.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?


    reviewer2793882

Monitoring has improved full-stack visibility and now provides faster, AI-driven root cause analysis

  • December 29, 2025
  • Review from a verified AWS customer

What is our primary use case?

I use Dynatrace in my project to monitor EC2 instances and ECS containers and track application performance, detect infrastructure, service, and container issues. In my project, I use Dynatrace for full-stack monitoring.

What is most valuable?

The best features Dynatrace offers include configuring alerts and dashboards, such as problem notifications and custom dashboards for EC2 health, ECS service performance, error rates, and latency, along with anomaly detection and security and IAM, allowing outbound traffic to Dynatrace and using IAM roles for EC2 with no sensitive data stored locally. In my project, I use Dynatrace OneAgent on EC2 and ECS to monitor the infrastructure, containers, and application performance, providing automatic service discovery, real-time metrics, distributed tracing, and AI-based root cause analysis.

What needs improvement?

Dynatrace can be improved by fine-tuning AI-based settings.

I feel that improvements around API rates and latency could be beneficial.

For how long have I used the solution?

I have been working in my current field for the past three to four years.

What do I think about the stability of the solution?

Dynatrace is stable in my experience.

What do I think about the scalability of the solution?

The scalability of Dynatrace is good.

How are customer service and support?

Customer support is excellent; whenever I raise a ticket with the vendor, they immediately connect with me and help me.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Previously, I used only CloudWatch, but I switched to Dynatrace because the features in Dynatrace are not found in AWS CloudWatch.

How was the initial setup?

Dynatrace is deployed in my organization in the AWS cloud.

What about the implementation team?

I did not purchase Dynatrace from the AWS Marketplace; I hosted Dynatrace on AWS.

What was our ROI?

I have seen a return on investment in terms of time saved.

What's my experience with pricing, setup cost, and licensing?

My experience with pricing is that it costs $58 per month for full-stack monitoring.

Which other solutions did I evaluate?

I did not evaluate other options before choosing Dynatrace, as I only selected Dynatrace.

What other advice do I have?

I advise anyone looking to set up a monitoring system in their project to consider Dynatrace because it will monitor their infrastructure, servers, and application performance, providing automatic service discovery and real-time metrics; it is the best option to choose or set up in their project. I gave this review a rating of 9 out of 10.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)


    Retail

Outstanding APM Solution for Seamless Application Monitoring

  • December 25, 2025
  • Review provided by G2

What do you like best about the product?
Dynatrace proved to be an excellent APM tool for applications that had integrated Dynatrace agents into their infrastructure, enabling effective monitoring and tracking.
What do you dislike about the product?
The support for monitoring and tracking traffic for applications hosted in the cloud feels somewhat cumbersome.
What problems is the product solving and how is that benefiting you?
It is likely that this product offers support for applications that are hosted in the cloud.


    Abednego Petrus

Unified monitoring has improved end-to-end visibility and accelerated root cause analysis

  • December 18, 2025
  • Review provided by PeerSpot

What is our primary use case?

My main use case for Dynatrace is for observability monitoring, specifically to know performance, end-to-end monitoring, and root cause analysis.

From the application side, we need monitoring for the latency, error rate, and request count for the transaction, and also for the digital experience; we want to monitor the analytics of user application. Additionally, for the infrastructure, we want to monitor the utilization of CPU, memory, disk, and network.

For monitoring transactional, it means how many transactions come to our customers in banking.

What is most valuable?

The best feature Dynatrace offers is APM. When I mention APM, I am referring to Application Behavior Monitoring, and database monitoring is what makes that feature stand out for me.

Database monitoring is very helpful to know the performance of query performance, meaning how much latency there is for the query once called from the application side, and if there is an error from the query, it indicates issues such as ORA errors from Oracle or other errors from PostgreSQL and MySQL or any DBMS.

Dynatrace positively impacts our organization because it is a unified monitoring solution that centralizes the performance of infrastructure, application, and database.

What needs improvement?

Dynatrace can be improved from the security side because other observability products are enhancing security features, while Dynatrace has room for improvement in this area.

For integration, Dynatrace can improve with WebMethod because it is quite common among our customers using that platform, and they want to monitor their transactions for ESB, which is middleware.

Dynatrace could improve its recommendations, which are not only for cause analysis but also for application performance, infrastructure, and database, including database tuning for the query. I would rate Dynatrace an eight for these reasons.

For how long have I used the solution?

I have been using Dynatrace for around six to seven years.

What do I think about the stability of the solution?

Dynatrace is stable.

What do I think about the scalability of the solution?

The scalability of Dynatrace is very significant, especially considering the current improvements in their features, and there is a big opportunity from Indonesia with many use cases for Dynatrace.

How are customer service and support?

The customer support from Dynatrace is very helpful, as they assist our customers effectively when there are problems on the platform side.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I have previously used different solutions such as Datadog and Instana because our customers are selling three products of observability.

What was our ROI?

For the investment, Dynatrace is very helpful for our customers because they can see the transactions through Dynatrace and save money by identifying problems, thereby reducing monetary losses on their application side.

What's my experience with pricing, setup cost, and licensing?

For pricing, we use the Classic model, specifically DPS, which stands for platform subscription. The cost can be controlled from our side, and it is very transparent with Dynatrace regarding DPS and licensing.

Which other solutions did I evaluate?

The first time we used Dynatrace, we did not evaluate other options, but later considered Datadog, Instana, and Elastic APM.

What other advice do I have?

My advice for others looking into using Dynatrace is that recommendations are very helpful for our customers, as many products provide numerous recommendations. However, Dynatrace focuses mainly on monitoring operations and providing root cause analysis without offering much in the way of recommendations, which I believe is important for observability products.

Our company has a business relationship with Dynatrace beyond being just a customer; we are both a partner for local support and a reseller for licensing. I rate this product an eight out of ten.


    Sourabh K.

Effortless Service Mapping and Insightful Dashboards

  • December 10, 2025
  • Review provided by G2

What do you like best about the product?
The way it automatically maps out services and dependencies is genuinely helpful, instead of guessing where an issue might be coming from, I can usually spot it pretty quickly. I also like how the dashboards pull everything together in a way that actually makes sense, even when there’s a lot of data flying around.

Another thing I appreciate is the alerts.
What do you dislike about the product?
There’s a lot of information packed into the dashboards, and it takes a while to get comfortable with where everything is and what each view actually means
What problems is the product solving and how is that benefiting you?
Instead of manually digging through logs or bouncing between different tools, it ties everything together and points me toward the actual root cause. That alone saves a ton of time during incidents.