Dynatrace Reviews

Our main use case for Dynatrace is that we deployed Dynatrace OneAgent across our AKS nodes to monitor pod level metrics and service dependencies. Smartscape topology helped us visualize the entire environment in real-time and identify issues such as memory leaks and high response times during load. For our backend services, we were facing intermittent latency issues, but using Dynatrace we could pinpoint the exact methods and queries causing the application slowness and understand what exactly was happening.

Dynatrace offers several best features. When comparing before integrating and using Dynatrace, we also used other tools including Prometheus and Grafana, but Dynatrace provides that additional feature. Nowadays, everything incorporates AI, and Davis AI that Dynatrace built-in dashboards are clean and powerful. The AI integration allows us to outperform the issues, reduce the downtime, and timely resolve the issues. Their AI integration is exceptional and gives Dynatrace a better capability compared to competitors.

Davis AI and the built-in dashboards have made a difference for our team because whenever we were stuck on any level issue or metrics and wanted to dig into some logs and metrics to identify where exactly it was going wrong on our application side, the AI helped us to narrow down where exactly it was going wrong. It identifies the particular specific pod, application, or container and provides a whole overview of the application and container level. We had to fine-tune it to align with our environment. We fine-tuned it in such a way that whenever something goes down on our containerization or VM level, we could drill down and by using the AI analysis, it looks into the entire system and provides an exact pinpoint solution when we give a detailed outline. This reduced the resolution problem to a lesser time compared to using other tools.

Dynatrace has positively impacted our organization. We have had major outages across the organization, whether application side or performance level related, with users experiencing slowness or blank pages. However, Dynatrace setup on an enterprise level brought down the outage time by half. All cross-functional teams can integrate and see exactly what is going on, allowing us to work on the actual resolution based on the metrics provided by Dynatrace. Using this tool, it pinpointed the problem instead of us scratching our heads trying to identify where it could go wrong, and we could directly proceed with the solution. This reduced our man-hours and outage time while increasing productivity based on performance metrics and observability.

We encountered some challenges while using Dynatrace. Although the initial setup was smooth, fine-tuning alert thresholds and custom metrics took some time. Another challenge was that Dynatrace charges based on host units, so we had to carefully plan our agent deployments. The licensing model is expensive. Additionally, the complexity of setup is an issue. While OneAgent and auto-discover services are powerful, the setup is more complex compared to other tools such as Prometheus and Grafana. These integrations are simple and basic, but Dynatrace setup requires more complexity based on the environment. For new users wanting to use Dynatrace, it is difficult. However, the AI-related solutions and metrics took us to the next level for identifying and fixing things.

Dynatrace requires an agent for operation. OneAgent is powerful, but it is also resource-heavy. On lightweight nodes or older systems, the agent can slightly impact performance. If Dynatrace could implement a lightweight agent behavior, we could make things faster. Additionally, if Dynatrace could add a long-term retention policy so that we could store more data and find fine-grained details, that would help us. While Dynatrace managed edition supports on-premises deployment, the SaaS version depends on cloud connectivity. For highly regulated or air-gapped environments, setup and updates can be challenging. Although the initial setup is smooth, if someone wants to fine-tune it and fully understand the tool end-to-end, it could be tricky.

Dynatrace is stable.

Dynatrace scalability is great. It is a powerful tool and helped us to reduce customer downtime and increase work efficiency. We could identify any issues causing problems in our application or environment.

Customer support is very prompt. Whenever we faced any issues, we could get timely resolution from their support, so we did not face any issues.

Positive

Before Dynatrace, we used open source Prometheus. It is a very standard solution but not exceptional. It is a standard option because it is open source and free.

My experience with pricing, setup cost, and licensing is that Dynatrace licensing model is based on host units and can be complex initially to understand. If setting up in a large scale environment, it is overwhelming because it is expensive. We had to plan carefully when deploying OneAgents across our nodes or clusters, ensuring we did not exceed our licensing capacity.

For purchasing Dynatrace, we explored the AWS Marketplace, but on an enterprise level, we reached out to their agents and they set up a call for integration. We deployed on an enterprise level because while the marketplace is fine, if implementing a solution at a huge enterprise level, we had to work with the actual Dynatrace team to set it up. For some of the bare metal hosts or engines, we went with the marketplace only.

When it comes to metrics and performance, we have clear return on investment. Before Dynatrace, we spent considerable time manually correlating logs, metrics, and traces from multiple tools to find root causes. Using Dynatrace directly improved application uptime and reduced customer impacting incidents. It helped our engineers focus on optimizing rather than firefighting.

My experience with pricing, setup cost, and licensing is that Dynatrace licensing model is based on host units and can be complex initially to understand. If setting up in a large scale environment, it is overwhelming because it is expensive. We had to plan carefully when deploying OneAgents across our nodes or clusters, ensuring we did not exceed our licensing capacity.

Before choosing Dynatrace, we considered DataDog and other tools available in the market, but compared to all other tools and their values that could bring to our organization, we chose Dynatrace.

My advice for others looking into using Dynatrace depends on the organization. My main advice is that if you want an enterprise-level observability and monitoring solution for a hassle-free experience with troubleshooting, identifying and reducing customer downtime, and increasing work efficiency, or if you want a stable and standard solution, Dynatrace is the best fit. This review received a rating of nine out of ten.

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.

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.

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.

Positive

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.

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.

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.

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.

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.

My main use case for Dynatrace is that we find it to be a good tool for working with establishing analytic models for our customers' front ends or providing dashboarding for customers in relationship to their operations.

Regarding my main use case with Dynatrace, it helps with the ability to formulate a single pane of glass in regards to working with automation and operations, including DevOps into an API or an MQTT model, which allows you to monitor the orchestration of how updates are being managed and handled, how effectively those deployments are progressing time-wise and personnel-wise, and to expedite the course of upgrades and so on without introducing infrastructure overhead while allowing everyone to see what is happening at once.

Dynatrace has positively impacted my organization because reporting is ongoing and constantly evolving to adapt to the new technologies that are being introduced, such as AI and other standard protocols of reporting and metadata. The key advantage here is that Dynatrace has a good position in this space by being flexible enough to accept variations and bring in unknown footprints of AI and APIs that will introduce new data sources, giving it a chance to be very flexible in receiving those new standards with very little overhead. Not everything can come in quickly, but many things have, and Dynatrace is particularly good at that.

Specific outcomes or metrics that show how Dynatrace has helped my organization include its helpfulness with RCA reporting for incident response. The key details here are that you have to understand when something does happen, whether it is a fault on the service side or a fault on the customer's side, and understand the brief hiccups that cause outages and impacts. The RCA reporting process for determining the cause, conducting a causal analysis, recovery causal analysis, and measuring the effectiveness of that response to justify and explain when things happen, specifically in the incident report response, has been valuable. When this is done holistically within the reporting analytics tool, it can greatly reduce the investigation time period to completion. The key detail here is that when an RCA investigator report is initiated, all of the top skill sets are engaged in that process, which represents a great deal of money and time that is lost because all team members, in their own capacity and relationship to the investigation, have to stop, do the analysis, reach a conclusion, do a follow-up corrective action item planning model, and schedule an ETA to get that accomplished. Those are very important details that take a lot of time, and Dynatrace helps reduce that time frame.

The best features Dynatrace offers are somewhat subjective as it does not do anything functionally unique compared to others. However, it does work very well with integrating into other environments or working in tandem with other environments. A reporting tool like Atlassian allows you to generate analytics reports for leadership structures and documentation in regards to that kind of support. This is valued because when we work with tools such as DataDog or New Relic and other major monitoring platforms, we can send all of that information into a very condensed leadership equivalency level reporting matrix that the leadership of your company can actually read, understand, and take steps with and act on because of the way that the tool comes in reporting-wise effectively up into the consolidated enterprise reporting metric systems, such as Atlassian.

Regarding the features, Dynatrace works in two different environments. Its siloed version, the older version, is usually hosted on local infrastructure, whereas its new possible format, the SaaS version of Dynatrace, offers additional value as well as beginning to solidify the AI models that will be under the hood for the Dynatrace engine SaaS model, which adds value opposed to looking at something the server version of the older release of Dynatrace. The value is that SaaS gives you that level of freedom, and of course, the MRU and SLA agreements that you have in place to support Dynatrace SaaS services give you an added level of security that your own siloed environments do not offer.

Dynatrace can be improved by focusing on the model because when you say single pane of glass, it means different things for different people. When you have a single pane of glass for your customer base, and let's say you have 190 customers, technically speaking, that is 190 dashboards that exist and at least a template format with some optimized additional monitoring requirements added to them. However, that is not the same as a single pane of glass for infrastructure, which Dynatrace also serves. There is also a single pane of glass for executive leadership of IT operations and environments, including automation and the SRE Director of Operations role. This is not the same as a single pane of glass for executive management, such as the CIO and CEO, which require a completely different type of set of tools. The preparation of FinOps for finance, SecOps for security, and for automation and operational roles needs to address the company requirements specifically in regards to grid systems or distribution systems. Each of these will have its own version of a single pane of glass, and that is something that Dynatrace needs to be more flexible on going forward.

I would also like to note that Dynatrace needs to have the ability to import additional types of imports beyond standard containers, images, and animations. Animation value does carry significance here and it would be valuable to be able to add that because animation is an initiator. Most companies that use animation in their environments tend to get faster responses and response times as opposed to simply using red, green, and yellow. This can add value to that discussion.

Other improvements needed for Dynatrace include understanding that one tool usually cannot meet all the requirements you need. Being aware of that means being more pragmatic about your approach. By introducing an additional tool or two to cover all the aspects and attributes, technology is always evolving, and you may find a lesser-level vendor who can monitor something newer than what your overall environment is monitoring with something such as Dynatrace. Dynatrace is not really a bad tool when working with other similar services, such as DataDog, New Relic, or Checkmk. Dispersing your resources in multiple baskets provides more reliability, sustainability, and better control of cost factors because you have an easier way of gauging costs between vendors versus services. The key thing is to ensure you have internal and external viewpoints and multiple potential tools such as Dynatrace to help you achieve 100 percent accountability and reliability.

I have been using monitoring tools for about six years, which includes Dynatrace.

Dynatrace is stable.

Dynatrace's scalability is to be determined since we are on SaaS and we have not had a scale event yet, but that is something we will be looking into as we develop the business continuity model.

Customer support for Dynatrace is good, and I have no issues. They have provided good services for our needs. I would rate the customer support an eight.

I previously used many solutions out there. The biggest driving force for me has been getting the most value for the investment for compatibility, integrability, and serviceability to a single pane of glass based on my requirements. This is an evolutionary thing, and while we may be using Dynatrace now, we might switch to something else such as New Relic or another type of tool or even progress to an open-source tool to better control costs in the future. However, all in all, Dynatrace is doing a good job, and we are using it for that reason.

I have seen a return on investment, as my example of ROI is that using a tool such as Dynatrace is an investment that reinforces the customer's desire to want to stay with us. This is crucial because as you integrate these processes, you also want to integrate the investigation process, what we call the RCA process. It is important to move forward with the least amount of time and man hours as necessary while keeping your involvement with other employees as minimal as possible. This enables you to complete the investigation as soon as possible, ultimately saving in operational overhead, productivity, and personnel resources.

Regarding my experience with pricing, setup cost, and licensing, the setup costs and licensing were not a problem for Dynatrace and have not been a problem for most monitoring services. The key issues that were upfront were information processing, data source processing, and housing. We understand that Dynatrace is in business to be in business, but these areas specifically are where you have runaway costs. Your initial investment in licensing costs pales in comparison to the question of why you would charge a license fee and usage for a tool if you are going to be three times higher in processing the data you are sending via the agents. It is really important to know that if you come across costs on the actual operational side, you can use other vendors to help offset that to a small degree, ensuring they do not have a cost covering from something such as data processing or data storage. Alternatively, you could use your infrastructure and local data centers to have an Amazon repository for logs and alerts to get those costs under control. Cost control is very important when using these tools.

I evaluated other options before choosing Dynatrace.

Regarding Dynatrace's AI capabilities, I think its governance and security are only as good as the leadership and the infosec overhead involved. Dynatrace has good templates to meet the AI compatible capabilities, but it always comes down to the human element in the environment. Proper correspondence and response are required at the human level to fully bring the power and capacity of the AI capabilities into its full effect.

The accuracy and reliability of output from Dynatrace are based on two very critical details. One is the contiguous articulation of input that comes in from all sources without interruption. Secondly, an overall average gives you the average reliability with said accuracy. This basically means that if you are tracking everything effectively, when you do have hiccups or impacts, using those capabilities will help identify where you have what we call black holes. The black holes deregulate and devalue the nature of the reliability of this kind of solution because the processing agent configurations may not be monitoring everything necessary, and the importance of the AI capabilities is to ensure they are identified, quantified, stood up, and put in place to help boost accuracy and reliability. That does not always happen and it is human-dependent and must be monitored to make sure that it is done correctly.

Dynatrace is deployed in my organization in both on-premises and some in public cloud that is also deployed with two other monitoring tools, both of which are SaaS-based. We use a SaaS provider for the public cloud deployment.

My advice to others looking into using Dynatrace is to document every application and every infrastructure resource that you have and ensure you place those into a central repository or a wiki. This will allow you to have that information in place to do a comparative design model and see if you even need Dynatrace in the first place. Small to mid-sized companies may or may not have a need for Dynatrace, but this is the most effective way to approach it. I give this review an overall rating of nine.

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.

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.

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.

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

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.

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.

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

Positive

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.

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.

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.

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.

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.

I would rate this product a 9 out of 10.

My main use case for Dynatrace is observability, monitoring, insights, performance, variation, dashboarding, services, traces, validation, cross-team collaboration, reporting, and many more.

As a senior performance analyst, I look into Dynatrace in terms of the observability parts, and mostly, there are multiple dashboards that have been created for multiple product groups from front-end layer to a back-end layer. I keep monitoring their performances, their failure, and their anomalies that have been detected through the problems page, alerting if it has been sent to the right team, and investigation on why these issues do occur, how are they recovered, and who would be the right team to contact. One of the newest cases would be when we had extremely high load on our application, and we were unable to figure out what was causing it. We looked into Dynatrace and noticed Apdex being down, high load days, and request errors being increased, and investigated to identify that it was the bots that got increased, but they were all coming as real users. We tried to investigate their user agents, we tried to investigate their IPs, connected through a bot manager system and CDN, and then mitigated the issue through content protector. We were able to improve our performance, our Apdex, and we did reduce our overall load on the site.

In terms of my main use case and other ways my team uses Dynatrace, I would say teams have collaborated. DevOps uses it for administrative purposes, including me, and then we have developers use it for investigative purposes on our lower environments like QA and Dev. We have a separate tenant specifically only for China users because they are restricted through firewalls and all of those things, so the servers are all set up within China, Tencent, providing a specific tenant only for them. These are most cases.

Dynatrace has impacted my organization positively in many ways because we have been using it for almost eight to nine years now. We have used Dynatrace day in and day out for performance improvements. The recent example I would share is from our front-end team, which used it in daily investigations of how our web vitals, including Google Web Vitals, are performing in terms of LCP, INP, DOM interactive, Time to First Byte, and other web vital metrics. We were able to figure out that some of our images or some of our JS scripts were the primary cause of these being down, and we were able to use Cloud and other agents through Dynatrace to find the slowest performing components, fix them, and we have been able to see those improvements. Our site is way better compared to three months ago.

To measure those improvements, we see that our LCP actually improved by about 42%, trending around 5.3 seconds on a median range, which we improved to around three seconds range. In the same phase, we also improved our TTFB by somewhere around 40-42% and DOM interactive by somewhere around 40-45%. We are also trying to improve on multiple other categories, not only on overall site performance but probably homepage performance, content performance, product page performance, search page performance, and others. These improvements are in progress.

The best features Dynatrace offers are many. I would say from dashboarding, alerting, integration with multiple applications, the new DQL features that come up with Dynatrace, the notebook feature, the workflows, the ready-made dashboard that Dynatrace provides, the page where you are able to track your license consumption, and the observability part where it provides the root cause for the incidents that appear.

Out of all these features, dashboarding has been a major contribution in my day-to-day work, looking at performance trends, failures, errors, and all of those things, and cross-verifying that with the problem detection that Dynatrace provides. Over the recent past, DQL has been a major help, especially for dashboarding purposes, investigative purposes, particularly through notebooks, since you do not have to run a dashboard always; you can just use very less license consumption and run a query to find out what the actual trend looks like or what the failure looks like and where exactly this is. Most of these are collaborated with Dynatrace Assist, AI Assist, and Cloud Assist through MCP servers, which has also been pretty helpful.

Certain configurations still require some navigation through multiple screens. Dynatrace offers many apps, but when it comes to training and documents or help from a point of view, it is very elaborative. You need to go find, search, look into the specific ones, and see how they are changing. Dynatrace currently offers both classic and Gen3 versions, so most of these documents are kind of updated with Gen3 while some users may be using the classic version, making these documents sometimes confusing regarding their availability for classic or Gen3 versions.

I would also like to add that the user interface has been helpful, allowing all the apps it connects to be accessible through a single stop or a button, where you can get all the apps and then look into them. So in terms of user interface, it is pretty helpful.

Service capabilities are great, user communities are great, the relationship with Dynatrace support, CSMs, or account managers has been great, consulting partnership is amazing, and the breadth of services is awesome.

Regarding Dynatrace's AI capabilities, I think its governance and security are handled well because until this date, there have been no complaints or issues we have come across. I agree that the governance has been taken care of, and all these CCNA, CCPA, and all PII level priorities are considered, so they have been good in that respect.

Regarding the accuracy and reliability of output of Dynatrace's AI capabilities, DTCTL has been great, and I would probably give it a percentage of somewhere around 80-85% on its accuracy. Through Dynatrace Assist, although it uses agent AI, there are times I have seen not satisfactory responses. So I would probably give it somewhere around 75%.

For others looking into using Dynatrace, all those examples I shared earlier in terms of pros have been great. I would say anyone really willing to purchase Dynatrace can use their test features for testing or POCs that Dynatrace would provide for approximately a month period. This would be helpful in understanding what the tool can provide and how beneficial it is for your organization. I rate Dynatrace a nine on a scale of one to ten.

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.

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.

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.

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.

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

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.

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.

I currently work as a Principal Consultant specialising in observability platforms at a technology consulting firm, AI OK. My role involves providing expert consulting on APM and observability tools, including Dynatrace, Datadog, and Splunk.

Previously, at Infosys and Ericsson, I led initiatives focused on observability platform adoption. Since February 2020, I have been designing and implementing centralized log management and observability solutions, with extensive hands-on experience in Dynatrace SaaS for performance monitoring and service reliability.

The problem detection and problem lifecycle presentation in Dynatrace is excellent. For example, when traffic increases from ten requests per minute to fifty requests per minute or even one thousand to twenty thousand requests per minute, I can see how the services' response time changes according to the traffic change and what the CPU time is for that particular request or API. This gives insight into all the components responsible for response time.

Another valuable feature is the ability to compare performance data from one week earlier or from the same time window on a previous day. This performance comparison capability is very helpful.

The ease of use is remarkable. While we have similar compute monitoring on Azure side such as Azure Monitoring and Azure App Services with compute utilization, Dynatrace links compute with services and services with code and other components. This makes problem management, alert management, and identifying what needs to be fixed for the development team much easier.

Through Dynatrace feedback, we were able to figure out bottlenecks, plan performance user stories, optimize execution time, and make numerous corrections. The problem lifecycle management is improved, and MTTR is very positive. For MTTD, or mean time to detect, it was previously taking hours and hours, but after implementing Dynatrace, even the L1 team can help detect and pinpoint bottlenecks. Not only has the time decreased, but the accuracy and quality of monitoring have improved significantly.

Problem detection has improved very positively, and the quality of monitoring has improved with the help of Dynatrace. We are saving time, saving workforce, and visibility has increased. Both technical and non-technical teams have greater visibility into how the application is performing.

One significant complaint I have raised with Dynatrace as a consultant is the availability of raw data for logs. While this capability exists, it is quite costly. The free allocation is five gigabytes, but comparing this with other tools such as DataDog, Splunk, or New Relic, the raw data availability on Dynatrace and the export of reports and UI aggregation features could add more value if enhanced.

Cost is a differentiator for Dynatrace. Additionally, security is becoming a feature, and AI-enabled security capabilities will add more improvement areas for Dynatrace.

Feature-wise, Dynatrace rates ten out of ten. However, when comparing feature versus cost, it rates eight out of ten. Not every client is one hundred percent on public cloud. There are hybrid scenarios with some on-premises and some private compute environments. In cases where compute is more CPU intensive, Dynatrace can be costly. Dynatrace is the best fit for customers using runtime compute, which covers approximately eighty percent of customers.

I have been using Dynatrace since February 2020.

There are no stability issues with Dynatrace. One limitation I found concerns agent installation. Although Dynatrace is a SaaS product with frequent agent management updates, installing the agent across all networks would benefit from more centralized management capabilities on Dynatrace.

Platform engineering and observability represent a journey through various tools. I started with open source and on-premises solutions involving flat file processing with the ELK stack. I then moved to using Azure Monitor, and subsequently adopted Dynatrace because of its focus on performance and APM capabilities. Dynatrace's APM features were highly recommendable, which is why I moved to this solution. Since cloud-native was important, I explored Azure Monitor as well.

The ROI is good. Compared with other tools such as DataDog or New Relic, both have their pros and cons with no complaints. However, Dynatrace is performing very well overall in terms of ROI versus investment.

When comparing tools such as DataDog or New Relic, both have their pros and cons with no complaints. Dynatrace is performing very well in terms of ROI versus investment.

If someone is looking for application fine-tuning and bottleneck identification on the UI side, services side, or network side, and they are using cloud as a platform, Dynatrace is the best tool to have everything in one place. I would rate this product eight out of ten overall.

The main use case for using Dynatrace is to check the CPU utilization and the performance stats of my load test, stress test, or endurance test.

During one of my tests, when I perform a load test, I parallelly open or configure the server of that application in Dynatrace, creating a new dashboard so that during my load test, I can easily observe what is happening, what the error stats are, what my pass percentage is, what my CPU utilization is, or the garbage collection, and other metrics.

I can even check my alerts and exceptions as well.

For me, the best feature Dynatrace offers is full-stack observability, which allows me to check my infrastructure or the containers because most of my applications are cloud-based, and with Dynatrace, I can check the database or the network path, or which are on-premises or cloud, making full-stack observability more suitable for me.

Dynatrace is our APM tool, which provides deep code-level visibility, allowing us to check the methods or exceptions, database calls, or external services, and we can easily trace them out.

Dynatrace has positively impacted my organization because usually when I do a load test, our API SLA is only one second, but it crosses more than three seconds or five seconds, and by using this APM tool, we can figure out what is causing it, what kind of error it is throwing, and how we can optimize it, making it very useful for my organization as well as for me while doing load testing.

For the metrics or numbers, our error rate should be less than three percent, and achieving less than three percent, even if it is one percent, is very good, and the reduction of the error rate by using Dynatrace was quite good.

Dynatrace itself is a very good platform where the UI interface is very simple and usable, but I would say if it were made even more simple, similar to our Splunk dashboard, that could help users or newer users understand it more easily, especially since sometimes I have seen when using Dynatrace, we are not able to add the time frame properly.

If you add some more fields with simple words or simple terms instead of the complex terms used for a resource, that might be helpful.

Dynatrace can be better and more user-friendly, and that is my advice, but overall, it is a good application and APM tool for a performance tester.

I have been using Dynatrace for four to five years.

Dynatrace is stable.

The scalability of Dynatrace is good, and we can easily figure out what is happening.

The customer support is responsive because when I logged some defects to the developer teams, they worked with Dynatrace team, and I think we have received much support.

Positive

Before using Dynatrace, I used AppDynamics and Splunk.

By using the APM tool for resource management and time management, we have saved a lot of time, so I would say this is a good investment that the organization has made.

I have not switched from AppDynamics as well as Splunk because I am using Dynatrace as well as those other two APM tools, depending on my project level, what the project is configured with, and which is better.

I would advise others to use Dynatrace because it is very good in terms of scalability and reliability, and the stats it shows, including the perfection and the graph, are very good, so I would suggest they use Dynatrace. I gave this review a rating of nine.

Dynatrace's main use case for our organization is incident management, primarily driving alerts, traces, and incident management for production servers on both Linux and Windows 2016 servers.

A specific example of how I use Dynatrace for incident management is that it provides our support team members with alerts if a certain service on a server is not working, there is a failure of a particular service, or the server is not performing as needed. We receive an incident for that and trace the server's services uptime using Dynatrace, which helps us diagnose the issue for both Linux and Windows servers.

Our main focus is maintaining the servers' uptime, and Dynatrace helps us minimize server downtime while providing applications and other services to our end user team.

Dynatrace's best features include alerts and the ability to monitor server health, such as CPU utilization, memory utilization, disk space utilization, as well as network services, and it also helps with application performance monitoring (APM).

I find server health check resources utilization, network monitoring, and APM most valuable for our team, as it helps our other cross-functional teams that require that data to track network health and application health. Dynatrace helps all of us in development and operations support, which makes it a really valuable tool.

Dynatrace has positively impacted our organization by helping us reduce downtime, as it was much higher before using Dynatrace. We are now able to minimize downtime for the servers and applications and easily trace and diagnose issues at the infrastructure level using Dynatrace, which is definitely helpful for enterprises using IT systems.

I give it a nine because the one percent improvement is required in itself, since if I provide a ten, then there is no room for improvement.

Dynatrace provides regular upgrades as a software used to provide server health checks, network monitoring, and application performance monitoring, so the team looking into Dynatrace's development provides regular updates. I don't think I can provide any improvements to Dynatrace as an end user.

I have been using Dynatrace for the last two plus years.

In my experience, Dynatrace is very stable and we don't need to do much additional work once it is installed and set up along with its configuration. There is nothing additional to manage about Dynatrace.

Dynatrace is scalable.

Customer support for Dynatrace is well-equipped, and they try to resolve queries if we contact them with any particular issue. They provide quick resolutions.

When I joined my client project work, they were already using Dynatrace, so I don't have any idea of what they were using before that.

Time is definitely saved with Dynatrace, as without it, it is very difficult for support team members to find out where the exact fault has occurred. With Dynatrace, we receive direct alerts on our Dynatrace console, allowing for much faster resolutions, so it definitely saves cost, efforts, and time.

Downtime has been reduced by almost thirty to forty percent in tracking and resolving issues, as Dynatrace logs, alerts, and traces help us go straight to the issue and try to fix it. Regarding cost savings, it has resulted in cost savings of mostly around twenty to twenty-five percent.

I don't have any idea about whether my organization evaluated other options before choosing Dynatrace.

I will definitely recommend Dynatrace as an APM, server health check, and network performance monitoring tool to be used by large-scale or mid-range organizations. I have no additional thoughts about Dynatrace. My review rating for Dynatrace is nine.

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.

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.

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.

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

Dynatrace is stable.

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.

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

Positive

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

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.

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.

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

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.