How Network Topolgy can be used to see network topology diagram for more then one resource group?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure
- Domain
- cloud, networking
Research direction
No file, test, or entry point is identified in the issue. First determine whether Azure Network Watcher Topology supports multiple resource groups, VNets, or subscriptions; done means documenting the supported scope or implementing and validating a multi-resource-group topology view.
Written by the indexing model from the issue text.
Description
Hello,
My orgnaziation is using hub & spoke architecture, and therefore we have few resource group, each resource group contains a vnet.
Clearly, we have vnet peerings & cross vnet communication.
I would really want know if and how Azure Network Watcher Topology can be used to see relations and network diagram of more then one resource group?
When I enter "topology" it enforces me to choose a single resource group, is there a way to avoid choosing resource group, and focusing on vnet? or choosing the whole subscription? or choosing few resource groups?
If this feature does not exist, it could be extremely usefull for my organization and I'm certain that for many other organizations as well, since it's very common to create vnets in more then one resource group, especially when working hub & spoke.
Thank you.
- Dominant language
- PowerShell
- Stars
- 114
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/NetworkMonitoring
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Te Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
Azure/NetworkMonitoring#30 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Azure/NetworkMonitoring#18 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Azure/NetworkMonitoring#17 ·
All issues in Azure/NetworkMonitoring
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug needs-triage service/elbv2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hashicorp/terraform-provider-aws#50100 · 1 comment ·