Calling out to all MS Azure Architects that have integrated with the new Dynatrace Cloud integration.
I'm wondering how you are integrating you Azure Platform Management Groups into Dynatrace when it comes to staging / production deployments.
We are separating Dynatrace Tenants by environment (one tenant for prod and one for non-prod). This is a good practice since Dynatrace Configuration is also treated as asset that is tested and shipped). Likewise on the Azure side there are two Management Groups also, but there are also platform-wide ressources that should be treated as "prod".
My Idea is to create a Azure connection in every tenant that focuses on the management groups, but I'm uncertain how everything that is ingested via event hubs should then be treated? I'm not an Azure expert but wouldn't then things like network gateways/connectivity, management, etc be pulled twice. Don't those things live outside of the management group?
My second thought was to connect both management groups into the prod Dynatrace tenant and only configure oneagents (VMs, VMSS, AKS) in the non-prod Azure Management Group to point to the non-prod Dynatrace tenant, while having the other stuff ingested to prod?
Does that make sense? Open for your suggestions/expertise.
Certified Dynatrace Master, Dynatrace Partner - 360Performance.net
