In my daily work, I use Dynatrace to check any DT alert that appears. It is mostly used to check any impact that has occurred and the alert which was situated in our environment. I generally receive these alerts through email, and the email contains a hyperlink. When I click on it and open it in a browser, it redirects me directly to Dynatrace. I open it and try to backtrace all the steps and try to find endpoints on what caused the error. If I am part of a claims center team, I can see where the memory saturation was or a high number of users threshold limit.

Recently, about one week ago, I received a DT alert. The DT alert indicates that I have to go directly and search using the DT specific number. An incident gets raised in the ServiceNow dashboard and I just copy that DT alert and go to Dynatrace and search it with that specific DT key as a primary key. When I search with that, I will find what is the root cause of it. The recent occurrence was memory saturation where the memory limit was hit as I was trying to scale up storage, but users exceeded the demand. I received this alert, but it was resolved automatically. I could see why it was happening. I backtraced a few steps and saw at which time the influx was more and why it was more. I could also see the service flow where I could see which batch gets executed at which time and after which batch what the workflow is. There are some jobs that run with reactivity in production. With reactivity means all the sequence of jobs get executed at the same time. Without reactivity means only that specific job gets executed. I could see the service flow that is all the reactivity process in production, including which batch is running after that in Dynatrace. Finding out endpoints is also what I find very intriguing because it is really good. I searched that and I solved that issue.

I have integrated Dynatrace into my Guidewire application. Guidewire is an insurance product which I use.

I mostly use Dynatrace to find the root cause and perform certain analysis and provide users why this sort of issue is occurring. The start and end points are mandatory and I also check the service flow, which enables me to know where the job is running and at which point it is and when will the next job be executed. Everything happens in a sequence. The visualization is what I find most interesting because having a visualization graph will enhance reading capacity and readability.

When I was solving a recent incident about memory saturation, what I found the best is the visualizations. Every particular reason, when and where it was impacted, suppose a part of memory was impacted, I can view it in any sort of format, a pie chart or a bar chart or a histogram. I can choose any type of graph based on my better readability. It is really convenient and it is easy to visualize where things have gone wrong and why things have gone wrong, why the influx was high, why the influx was low. I can analyze whether my scaling capacity increased or not. I get to analyze everything. The visualization is the best feature.

I have never faced any sort of downtime issues when working with Dynatrace. The visualizations are the next best feature. If I did not have any visualizations and got a DT alert, just looking through clustered information would take a considerable amount of time and energy. Having graphs and charts enables me to know where and at which time the saturation point was high or at which point the saturation time was low. I could compare that specific graph with the same day or perform a weekly analysis or a monthly analysis, and it will be crystal clear. Humans can remember more what we see than what we read. Visualization helps me a lot. It saves a lot of time. If I were spending around five hours on a Dynatrace task, it saves around one to two hours easily. It makes me faster and I get to give accurate solutions.

One of the features that I find intriguing is I can go through business analytics dashboards. That concatenated dashboard enables me to see which processes and which jobs are running parallelly, simultaneously. One job will not be running singularly in my specific environment. At the same time, multiple jobs might be running. In case an incident pops up and I need to check the service flow, I just go to that specific job ID and search the workflow, service flow of that particular branch and know where it is. It helps me in segregating most of the information which is clustered generally.

One big thing is the learning curve. It can feel overwhelming at first, especially for new users. When I started as a fresher, it felt a huge hurdle for me to cross. Simplifying the onboarding experience or adding more guided walkthroughs would be appreciated. The UI also can sometimes feel more clustered, especially when navigating across multiple services or dashboards. I want it to be more intuitive. I want it to be more customizable so that I could improve the usability of it. Of course, the licensing and setup cost are also slightly expensive.

I have been working for around 1.4 years in my current field and I have been using Dynatrace for around eight months.

I would say Dynatrace is very stable because till now I have never faced any sort of downtime issues. If any downtime issue were to be faced in production, I would probably have a global outage. Dynatrace is very stable.

Dynatrace's scalability is one of the best features. Whenever there is a huge number of users and when I am expecting at a certain time, suppose at 6:00 to 7:00, that would be a huge rush hours where a lot of users try to log in and try to do many changes in their respective profile. I scale up storage and Dynatrace tries to adapt pretty well to my growing needs. I am switching to version 10, moving to cloud, and it is scaling pretty well.

I reached out initially because the UI was pretty complex. For a beginner who has to use Dynatrace, I would say they would face considerable challenges. I reached out to customer support and they were really helpful. I reached out to them ten to fifteen times and they did provide proper documentation. That documentation was huge, so they helped me pinpoint using certain keywords. They literally taught me what to do.

I did not use any other solution prior to Dynatrace. This was the first product that I ever used as soon as I entered the market and I am continuously using it till now.

At the beginning, I did face a considerable amount of challenges because the UI was not that customizable. I had to reread the entire documentation that Dynatrace provided. Bit by bit, it took me a little bit of time in setting up, but once I got used to it, it is pretty straightforward.

Everything was pretty smooth. My managing team did not face any difficulties when they were trying to set up everything and licensing related activities, but the cost is slightly more expensive and is on the expensive side. I would appreciate it if they could reduce the cost or make it more customizable.

This is a great return of investment because it saved me a lot of time. My team tends to face Dynatrace issues every week, around twelve to fifteen of them. Whenever an incident pops up, I try to spend less time on working on incidents and more time working on enhancement. If I were to work five hours on a Dynatrace incident, I think I would save one or two hours because of its visualization capabilities and its workflow which shows me everything. I saved a lot of money as well because I did not recruit any new developers as soon as I started this product. I saved time and money.

Everything was pretty smooth. My managing team did not face any difficulties when they were trying to set up everything and licensing related activities, but the cost is slightly more expensive and is on the expensive side. I would appreciate it if they could reduce the cost or make it more customizable.

My team did try to review other options, but I felt Dynatrace was the best in the market. After carefully reviewing, I read comments from others and visited other projects and other project members showed me the flow and how it improved it. I just moved on with it.

I would not recommend this to a small project team or any other small teams because this is slightly a costlier product. Of course, the readability and visualizations are pretty noticeable features that anyone would want, but the pricing is not worth it for small teams because I would try to evaluate more options. Dynatrace is the best product in the market. It might be difficult to learn at first, but when you try to spend more time on it, reading everything, the analysis is very top of the line. The ability to backtrace is important because I will know where things have gone wrong. Similar products in the market, similar to Dynatrace, do not provide the ability to backtrace. Backtracing is one of the important steps. I give this product a review rating of nine out of ten.

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.

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.

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.

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 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.

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.

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.

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.