G2

Caleb S.

Sr. Cloud Engineer

Enterprise (> 1000 emp.)

1/4/2019

"Frustrating implementation with negative impact updates"

1.5/5

What do you like best about Dynatrace?

The layout is great. Service chains make it easy to see how each service is calling everything else. Sprawling connectivity view to see how the environment interconnects. Users are able to easily use this version. Review collected by and hosted on G2.com.

What do you dislike about Dynatrace?

Difficult to implement a hosted solution. Dynatrace oneagent updates sometimes fail requiring manual intervention. Recent updates have caused major service disconnects. Missing service data or transactions. Metrics are skewed due to the missing data. Very sensitive AI causes false alarms (0.001ms response time change creates a service ticket) Review collected by and hosted on G2.com.

Recommendations to others considering Dynatrace:

Implementation hassle was high. Consider using Dynatrace's hosted solution if possible.

Be sure you have a tagging plan in mind to properly segregate services. There's a hidden limit to services that are tagged the same way, causing us to rearchitect parts of the implementation.

If you plan to use the UEM features, be sure your applications have some way of identifying users in the code so every transaction doesn't show up as anonymous. Review collected by and hosted on G2.com.

What problems is Dynatrace solving and how is that benefiting you?

Monitoring of applications and performance. We have received a better overall view of interconnectivity between apps in our environment. Helps show widespread problems assuming it catches the right transactions and doesn't miss data. Review collected by and hosted on G2.com.

Current UserValidated ReviewerIncentivizedSource: Seller invite