Dynatrace Reviews

Releasing a new product and going from an AS/400 to a Microsoft environment. 

We obtained a better insight into our environment and consolidated a lot of our old apps into one app. 

We are still implementing Dynatrace. We are in the process of a PoC to discover why our sync test failed. It also gave us the cause of what was at fault.

PurePath gave our developers some tools that they did not know existed, and they gained a faster, more robust use case.

It needs education and training to ensure you get the full value of your purchase. Maybe add in a certification for Dynatrace.

• Operational monitoring: How services ran in the last five minutes.
• NOC screens together with GTM monitoring.
• Troubleshooting of problems occurring in communication between microservices down to the code level.

• Reduced MTTR, thanks to smart problem detection and automated root cause analysis.
• Proactive monitoring of occurring problems and outages warnings.

• Automated dependency identification for HTTP conversations between microservices stack enables monitoring of microservices-oriented architecture. 
• .NET core and Spring code level analysis helps with root cause analysis.

.NET core support to the level of Java (at the moment, it is limited).

Custom reporting capabilities should be extended, because it now has basic charting capabilities. Alternatively, Dynatrace can create a bunch of plugins to popular BI platforms (e.g., Microsoft Power BI). All to allow custom reporting as well as SLA-oriented reporting. 

Our primary use use is to monitor apps in terms of performance and availability.  

We can analyse problems more quickly, and detecting problems becomes easier with Dynatrace.                               

PurePath: The transaction structure can be seen by any user.                                            

Under heavyweight, Dynatrace becomes slower when listing PurePaths. 

• It is now easier to install and start using it. Installation used to be complicated with AppMon.
• Also, the user tracking and session play are great.

• Autodiscovery of services and architecture 
• User tracking and session (with errors) recording and reproducing.

Searches should be faster. 

• Pricing is still too expensive.
• Their proof of concept is still a bit difficult.

It looks nice. The service discovery and user play are really surprising.

Use case monitoring of our shop floor systems. 

We use it for acceptance and production environments, which are SAP based.

We can report and monitor specific use cases which could not be monitored with SAP or other tooling. 

As of v.7.0, it is possible to use the web UI. Before that, it was too difficult using only a fat client

UEM can be used for user impact analysis and troubleshooting. We have applied this to prove that a specific issue originated from the back-end and was related to a specific user function.

Bring the interface to the same level as OneAgent. v.7.1 is a good improvement, but it has not been integrated into our environment yet.

One to three years.

We have all our infrastructure in the cloud. 

This tool helps us gather information from all hosts and services, then cross reference the information.

Although, we are still implementing it, we have some servers using Dynatrace. We have been using it to find bugs in our production environment.

The cloud integration, because it allows us to monitor serverless services as well as Docker containers, etc. 

I also like the "session replay".

They could improve their price ranges, as there is no option for startups or testing.

It has all the things an enterprise needs.

The primary use case is for application performance and analytics. We use it to monitor our on-prem Windows and Linux apps as well as our AWS and Azure cloud instances.

• Faster MTTR
• A proactive Ops team

We used to rely on multiple operations tools to monitor and obtain bits and pieces. Now, we have it all in a single pane of glass.

• Artificial intelligence
• Log analytics
• Being able to identify and correlate issues, and avoid them occurring in the future.

It needs certain UI changes to make going back to certain Windows easier. Certain windows open up in a different category with different set values and throw you off if you are not used to it.

We are using it in our AWS environment for monitoring health and application performance for roughly 400 instances running thousands of Docker containers.

• Improved visibility on performance and application issues.
• Automatic instrumentation of new services and technology without the need to install specific agents or modules.

• OneAgent
• AI-powered problem analysis
• Pre-configured alerts
• AWS integration
• API interface 

• SSO options are missing.
• JIRA integration should be enriched and more granular.
• Filters should have a “negative” option.