Dynatrace rebuilt monitoring around automatic discovery, then used its enterprise customer base to move the new platform into production.
Changing technical requirements
By 2016, large organizations were running applications across private infrastructure and public clouds. Containers and microservices changed the components involved in a transaction, sometimes while that transaction was being monitored. Tools configured around stable applications and manually maintained relationships required repeated adjustment and made it difficult to connect an end-user problem to its underlying cause. DT1
Step 1 of 4 · 2014–19
Dynatrace started its rebuild in 2014 and made the new platform commercially available in 2016. OneAgent instrumented systems automatically, while SmartScape mapped dependencies and Davis analyzed their relationships. The product joined application, infrastructure and user-experience monitoring in a shared view. DT1
The benefit was less manual work whenever the environment changed. Teams investigating an application failure needed current relationships among services, not another static dashboard. Astasia Myers’s S-1 analysis identifies that combined architecture as the product side of the transition. The rebuilt platform reached 1,364 customers by March 2019. DT1 DT2
Rivals AppDynamics, New Relic and infrastructure-monitoring tools were the named alternatives in the filing. Automatic discovery addressed configuration burden; the reviewed record does not establish that every named rival lacked it.
Step 2 of 4 · 2017–19
Dynatrace stopped selling its Classic products to new customers and concentrated on the rebuilt platform. Of the platform customers added since April 2017, 47% were existing customers who added or converted to it, and 53% were new customers. The new platform therefore benefited from an established sales relationship while also attracting fresh accounts. DT1
This matters to the growth explanation. A rapid rise in platform customers included a deliberate migration from older products, so it cannot all be read as displacement of competitors. The existing base gave Dynatrace a practical way to introduce the rebuild, and the company maintained both SaaS and customer-hosted Managed deployment options. Large organizations could change their monitoring platform without first adopting the same hosting policy. DT1 DT2
Rivals Existing customers could remain on Classic, move to the new platform or evaluate competitors. The customer mix demonstrates both migration and new acquisition, not the origin of every competitive win.
Step 3 of 4 · 2016–25
Dynatrace sold through direct teams and partners, targeting large organizations with complex environments. Its 2019 filing described free trials, product specialists and customer-success support as parts of adoption. It reported a 140% dollar-based net expansion rate for the new platform at March 2019. DT1
The platform could grow inside accounts as customers monitored more of their estate. That distribution system was costly: selling and marketing consumed a substantial part of revenue. 451 Research also cautioned that the subscription category included several contract forms, so the transition should not be reduced to a move into hosted SaaS. By March 2025, total ARR reached $1.734 billion, showing that the business continued to grow well beyond the original conversion period. DT3 DT4
Rivals New Relic and other vendors also sold observability subscriptions. The relevant distinction is the combination of a rebuilt platform, deployment choice and an enterprise sales channel.
Step 4 of 4 · 2017–20
CTO Bernd Greifeneder described using automated deployment, monitoring and remediation in Dynatrace’s own service operations. His account reports that the share of customer-identified production bugs stayed around 7% to 8% from 2017 to 2019 while SaaS and Managed customer numbers more than doubled. DT5
That operating choice supported a product sold on continuous discovery and analysis: the service itself needed to absorb more customers and changes without matching every increase with manual intervention. Myers’s analysis draws attention to the financial strain of the transition. Reading the two together explains both the investment and the operating problem it was intended to solve. DT2 DT5
Rivals The relevant alternative was continuing to scale manual service operations with customer growth. The CTO account provides an internal operating observation, not a comparison of rival support organizations.
Oldest first.