Dynatrace Reviews

Our primary use case is performance improvements and understanding the customer struggle. Dynatrace gives us real-time data that we can use within the office to display data.

• Greater insight into the customer experience and front-end user experience. 
• Bespoke dashboards and reports which help our business to grow.

• Bespoke business transactions providing greater performance insight. 
• Adaptable business transactions which can accommodate new developments.

• Needs a greater meta data capture.
• Usability on the front-end for non-technical people. Although, it does prove great support and problem solving collaboration.

• Application monitoring
• Software performance issues
• Learning application functions
• Tracking issues

Provides more visibility into applications.                                                                     

• AI functions
• Problem visibility, etc.                                                                

• Provide even more details about problems.
• Needs a clearer view for Smartscape.                                      

Customers want to monitor .NET applications and real user monitoring on online banking applications for desktop and mobile.

Dynatrace shows the customer path, common errors on desktop and mobile, and allows us to achieve faster page loads.

PurePath does deep dive analysis, has dashboards, and provides real user experience monitoring. It has allowed us to do analysis which was never possible before.

• Provide much better alignment between AppMon and Dynatrace. 
• Add support for Ruby.
• Make sure older frameworks, like PHP 5.3, are supported.

Our core application is still running on a Java Client-server based architecture. We provide that application as a service by hosting it (hybrid cloud approach). 

We needed a tool that would provide insights into the application and support troubleshooting activities in order to reach our SLA objectives.

It has delivered on its promises and is now the single trusted source of information for various actors of the service support processes.

Its ability to correlate a large source of information to pinpoint a root cause. This speeds up issue resolution and allow us to better reach our objectives.

Dynatrace SaaS still lacks configuration API or command line which would allow moving configuration from one tenant to the other.

We mainly use the tool to do performance monitoring of our customer environments. Internally, we check how our software behaves when we are developing it.

Developers love the tool, because it is easy to use. They can immediately see how their code behaves.

PurePaths are the best. We can see everything that we need from them. Problem detection is also giving us valuable information.

Waiting for the session replay, because it seems to bring the end user interactions available for the developers.

We use it to see a clear view of the system overall and monitor applications effectively and proactively. We also use it on our core software.

It collects and analyses information with AI, which is useful.

Session recording is one of the innovative features, which could be very useful for developers and the marketing team.

Regarding features, it would be good if there would be some features regarding app security.

It is quite expensive for startups. 

We are using Dynatrace to monitor our core application of the bank system. It is used especially in technical metrics monitoring.

Dynatrace improved the resolution of problems by making it easier to find root causes and easier to predict bad system behaviour.

The web dashboards are quite useful, good looking, and easy to use.

• The product could be faster and lighter, especially the rich client which uses many resources. 
• Graphically, it is not good.

• Load testing in R&D to anticipate bottlenecks. 
• Used in production environments to retrieve consistent use cases.

• Mean time to root cause analysis decreased drastically. 
• It allows us to address issues directly. 

The NeoLoad plugin is awesome, and it gets results from load tests correlated with test scenarios. 

C language integration requires manual implementation through the SDK, which is rather difficult and time consuming.