My company is planning to deploy Dynatrace, but our team already uses Application Insights. I'm concerned about duplicated telemetry, extra cost, agent overhead, and operational complexity. Rather than interfering with the deployment, I want to understand whether both tools can run together, what trade-offs to evaluate, and how to make a fact-based case for or against adopting Dynatrace.
3 Answers
Both tools can run at the same time, and some teams do exactly that. The important questions are data duplication, performance overhead, licensing, alert ownership, dashboard maintenance, and who will operate each platform. If you oppose the rollout, document those concerns and propose a controlled pilot instead of sabotaging anything.
Dynatrace generally offers broader observability features than Application Insights, but it is also more expensive and requires proper onboarding and operational planning. Compare the capabilities your organization actually needs, such as infrastructure monitoring, distributed tracing, service dependencies, user experience monitoring, and automated analysis. Then build a business case based on measurable cost and value.
A good compromise may be to instrument applications with OpenTelemetry where practical. That reduces dependence on vendor-specific SDKs and gives the organization more flexibility about where telemetry is sent. You can also run a time-limited proof of concept and define success criteria before committing fully to either platform.
The key is to make the decision through an approved evaluation: compare equivalent workloads, estimate ingestion costs, measure application overhead, and decide which system will be the source of truth for alerts and incidents.