Skip to content

Commit be7e8b1

Browse files
committed
Fix redirects for deleted Connection Monitor files
- Add redirects for configure-connection-monitor.md, connection-monitor-alerts.md, and connection-monitor-overview.md to point to how-to-configure-connection-monitor.md - Fix broken links in expressroute-introduction.md to reference the correct file - Redirects added to main .openpublishing.redirection.json file in the ExpressRoute section
1 parent c242872 commit be7e8b1

2 files changed

Lines changed: 15 additions & 16 deletions

File tree

.openpublishing.redirection.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -475,6 +475,21 @@
475475
"redirect_url": "/previous-versions/azure/expressroute/expressroute-migration-classic-resource-manager",
476476
"redirect_document_id": false
477477
},
478+
{
479+
"source_path": "articles/expressroute/configure-connection-monitor.md",
480+
"redirect_url": "/azure/expressroute/how-to-configure-connection-monitor",
481+
"redirect_document_id": false
482+
},
483+
{
484+
"source_path": "articles/expressroute/connection-monitor-alerts.md",
485+
"redirect_url": "/azure/expressroute/how-to-configure-connection-monitor",
486+
"redirect_document_id": false
487+
},
488+
{
489+
"source_path": "articles/expressroute/connection-monitor-overview.md",
490+
"redirect_url": "/azure/expressroute/how-to-configure-connection-monitor",
491+
"redirect_document_id": false
492+
},
478493
{
479494
"source_path": "articles/api-center/discover-shadow-apis-dev-proxy.md",
480495
"redirect_url": "/previous-versions/azure/api-center/discover-shadow-apis-dev-proxy",

articles/expressroute/expressroute-introduction.md

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -110,22 +110,6 @@ Key features that ExpressRoute Direct provides include, but aren't limited to:
110110

111111
For more information, see [About ExpressRoute Direct](./expressroute-erdirect-about.md).
112112

113-
### Connection Monitor
114-
115-
Connection Monitor provides end-to-end monitoring for your ExpressRoute connections, helping you proactively identify and troubleshoot connectivity issues before they impact your workloads. Unlike traditional monitoring tools that only track individual components, Connection Monitor continuously tests your entire ExpressRoute path—from your on-premises servers through the ExpressRoute circuit to your Azure workloads—with hop-by-hop path visualization to quickly pinpoint problem locations.
116-
117-
Key capabilities include:
118-
119-
* **End-to-end visibility**: Monitor connectivity between your on-premises network and Azure resources across your ExpressRoute circuit with continuous synthetic traffic testing.
120-
* **Performance tracking**: Track latency, packet loss, and connection availability in real-time with historical data for trend analysis.
121-
* **Proactive problem detection**: Automatically detect connectivity and performance degradation with configurable alerts that notify you of issues before they impact production.
122-
* **Precise troubleshooting**: View hop-by-hop network path visualization to quickly identify whether issues are in your network, Azure's infrastructure, or the connectivity provider's network.
123-
* **No additional cost**: Connection Monitor is available at no additional charge when configured through the Azure portal for ExpressRoute connections.
124-
125-
Connection Monitor is powered by Azure Network Watcher and provides insights into both ExpressRoute private peering and Microsoft peering connections. The service automatically creates bi-directional tests between your selected on-premises and Azure endpoints, with a default alert rule that fires when connectivity issues are detected.
126-
127-
For more information, see [Connection Monitor for ExpressRoute overview](connection-monitor-overview.md) and [Configure Connection Monitor for ExpressRoute](configure-connection-monitor.md).
128-
129113
### Bandwidth options
130114

131115
You can purchase ExpressRoute circuits for a wide range of bandwidths. The supported bandwidths are listed as follows. Be sure to check with your connectivity provider to determine the bandwidths they support.

0 commit comments

Comments
 (0)