Skip to content

[Automated Tracing] Enable support for Remote Gateway when using Virtual Network Peering #602

Description

@arudell

Is your feature request related to a problem? Please describe.
Right now when investigating Gateway scenarios where VNET peering is in place, the automated tracing is not able to discern the remote gateway it should be routing traffic to. Because of this, it never enables the tracing on the corresponding Gateway VM hosting the Virtual Gateway.

Describe the solution you'd like
In instances where VMs are part of a VNET Peering that leverages a remote gateway transit, we should extend the automated tracing functionality to detect the peering and isolate the appropriate remote gateway that traffic should be flowing.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions