Open GraemeCThompson opened 3 years ago
One possibility would be to move to a 2 pass approach to building the graph.
Stage 1: Gather all information about all resources
Stage 2: try and build the graphs relationships.
It may also help with representing resources that are referenced outside the resource groups provided to show more context.
This would be incredibaly use full. We have 5 different resource groups where the network team manages the network, we manage the VMs.. other team manages the log analytics.. having a single overview.. would be really really great
Can agree with previous comments, this would be an awesome feature. Most configurations in Azure have compute and network separated in different resource groups. Would be nice to have a parameter to "Follow dependency outside of Resoruce Group - true/false"
Yes, i agree to ! Ressources group are a with for my compagny to split from projets to apply RBAC and the subscription is just a financial spliting ! So for Ops like me, have a view that follow dependency to have teh realy of our Azure infrastrcuture will be amazing.
It appears that currently the resource groups are all treated independently when identifying relationships. One example is when networking resources are in one resource group and the VM resources are in another. The NICs in the networking resource group are not shown as linked to the VM resources in the VM resource group.