You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/expressroute/expressroute-monitoring-metrics-alerts.md
+5-64Lines changed: 5 additions & 64 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn about Azure ExpressRoute monitoring, metrics, and alerts usin
4
4
author: duongau
5
5
ms.service: expressroute
6
6
ms.topic: how-to
7
-
ms.date: 03/31/2024
7
+
ms.date: 06/24/2024
8
8
ms.author: duau
9
9
---
10
10
@@ -24,10 +24,12 @@ Once a metric is selected, the default aggregation is applied. Optionally, you c
24
24
25
25
> [!IMPORTANT]
26
26
> When viewing ExpressRoute metrics in the Azure portal, select a time granularity of **5 minutes or greater** for best possible results.
27
-
>
27
+
>
28
28
> :::image type="content" source="./media/expressroute-monitoring-metrics-alerts/metric-granularity.png" alt-text="Screenshot of time granularity options.":::
29
29
30
-
### Aggregation Types:
30
+
For the ExpressRoute metrics, see [Azure ExpressRoute monitoring data reference](monitor-expressroute-reference.md).
31
+
32
+
### Aggregation Types
31
33
32
34
Metrics explorer supports sum, maximum, minimum, average and count as [aggregation types](../azure-monitor/essentials/metrics-charts.md#aggregation). You should use the recommended Aggregation type when reviewing the insights for each ExpressRoute metric.
33
35
@@ -37,67 +39,6 @@ Metrics explorer supports sum, maximum, minimum, average and count as [aggregati
37
39
* Min: The smallest value captured during the aggregation interval.
38
40
* Max: The largest value captured during the aggregation interval.
39
41
40
-
### ExpressRoute circuit
41
-
42
-
| Metric | Category | Unit | Aggregation Type | Description | Dimensions | Exportable via Diagnostic Settings? |
43
-
| --- | --- | --- | --- | --- | --- | --- |
44
-
|[ARP Availability](#arp)| Availability | Percent | Average | ARP Availability from MSEE towards all peers. | Peering Type, Peer | Yes |
45
-
|[BGP Availability](#bgp)| Availability | Percent | Average | BGP Availability from MSEE towards all peers. | Peering Type, Peer | Yes |
46
-
|[BitsInPerSecond](#circuitbandwidth)| Traffic | BitsPerSecond | Average | Bits ingressing Azure per second | Peering Type | Yes |
47
-
|[BitsOutPerSecond](#circuitbandwidth)| Traffic | BitsPerSecond | Average | Bits egressing Azure per second | Peering Type | Yes |
48
-
| DroppedInBitsPerSecond | Traffic | BitsPerSecond | Average | Ingress bits of data dropped per second | Peering Type | Yes |
49
-
| DroppedOutBitsPerSecond | Traffic | BitPerSecond | Average | Egress bits of data dropped per second | Peering Type | Yes |
50
-
| GlobalReachBitsInPerSecond | Traffic | BitsPerSecond | Average | Bits ingressing Azure per second | PeeredCircuitSKey | Yes |
51
-
| GlobalReachBitsOutPerSecond | Traffic | BitsPerSecond | Average | Bits egressing Azure per second | PeeredCircuitSKey | Yes |
52
-
|[FastPathRoutesCount](#fastpath-routes-count-at-circuit-level)| Fastpath | Count | Maximum | Count of FastPath routes configured on the circuit | None | Yes |
53
-
54
-
>[!NOTE]
55
-
>Using *GlobalGlobalReachBitsInPerSecond* and *GlobalGlobalReachBitsOutPerSecond* will only be visible if at least one Global Reach connection is established.
56
-
>
57
-
58
-
### ExpressRoute gateways
59
-
60
-
| Metric | Category | Unit | Aggregation Type | Description | Dimensions | Exportable via Diagnostic Settings? |
61
-
| --- | --- | --- | --- | --- | --- | --- |
62
-
|[Bits received per second](#gwbits)| Performance | BitsPerSecond | Average | Total bits received on ExpressRoute gateway per second | roleInstance | Yes |
63
-
|[CPU utilization](#cpu)| Performance | Count | Average | CPU Utilization of the ExpressRoute Gateway | roleInstance | Yes |
64
-
|[Packets per second](#packets)| Performance | CountPerSecond | Average | Total Packets received on ExpressRoute Gateway per second | roleInstance | Yes |
65
-
|[Count of routes advertised to peer](#advertisedroutes)| Availability | Count | Maximum | Count Of Routes Advertised To Peer by ExpressRouteGateway | roleInstance | Yes |
66
-
|[Count of routes learned from peer](#learnedroutes)| Availability | Count | Maximum | Count Of Routes Learned From Peer by ExpressRouteGateway | roleInstance | Yes |
67
-
|[Frequency of routes changed](#frequency)| Availability | Count | Total | Frequency of Routes change in ExpressRoute Gateway | roleInstance | Yes |
68
-
|[Number of VMs in virtual network](#vm)| Availability | Count | Maximum | Estimated number of VMs in the virtual network | No Dimensions | Yes |
69
-
|[Active flows](#activeflows)| Scalability | Count | Average | Number of active flows on ExpressRoute Gateway | roleInstance | Yes |
70
-
|[Max flows created per second](#maxflows)| Scalability | FlowsPerSecond | Maximum | Maximum number of flows created per second on ExpressRoute Gateway | roleInstance, direction | Yes |
71
-
72
-
### ExpressRoute Gateway connections
73
-
74
-
| Metric | Category | Unit | Aggregation Type | Description | Dimensions | Exportable via Diagnostic Settings? |
75
-
| --- | --- | --- | --- | --- | --- | --- |
76
-
|[BitsInPerSecond](#connectionbandwidth)| Traffic | BitsPerSecond | Average | Bits ingressing Azure per second through ExpressRoute gateway | ConnectionName | Yes |
77
-
|[BitsOutPerSecond](#connectionbandwidth)| Traffic | BitsPerSecond | Average | Bits egressing Azure per second through ExpressRoute gateway | ConnectionName | Yes |
78
-
79
-
### ExpressRoute Direct
80
-
81
-
| Metric | Category | Unit | Aggregation Type | Description | Dimensions | Exportable via Diagnostic Settings? |
82
-
| --- | --- | --- | --- | --- | --- | --- |
83
-
|[BitsInPerSecond](#directin)| Traffic | BitsPerSecond | Average | Bits ingressing Azure per second | Link | Yes |
84
-
|[BitsOutPerSecond](#directout)| Traffic | BitsPerSecond | Average | Bits egressing Azure per second | Link | Yes |
85
-
| DroppedInBitsPerSecond | Traffic | BitsPerSecond | Average | Ingress bits of data dropped per second | Link | Yes |
86
-
| DroppedOutBitsPerSecond | Traffic | BitPerSecond | Average | Egress bits of data dropped per second | Link | Yes |
87
-
|[AdminState](#admin)| Physical Connectivity | Count | Average | Admin state of the port | Link | Yes |
88
-
|[LineProtocol](#line)| Physical Connectivity | Count | Average | Line protocol status of the port | Link | Yes |
89
-
|[RxLightLevel](#rxlight)| Physical Connectivity | Count | Average | Rx Light level in dBm | Link, Lane | Yes |
90
-
|[TxLightLevel](#txlight)| Physical Connectivity | Count | Average | Tx light level in dBm | Link, Lane | Yes |
91
-
|[FastPathRoutesCount](#fastpath-routes-count-at-port-level)| FastPath | Count | Maximum | Count of FastPath routes configured on the port | None | Yes |
92
-
93
-
### ExpressRoute Traffic Collector
94
-
95
-
| Metric | Category | Unit | Aggregation Type | Description | Dimensions | Exportable via Diagnostic Settings? |
96
-
| --- | --- | --- | --- | --- | --- | --- |
97
-
| CPU utilization | Performance | Count | Average | CPU Utilization of the ExpressRoute Traffic Collector | roleInstance | Yes |
98
-
| Memory Utilization | Performance | CountPerSecond | Average | Memory Utilization of the ExpressRoute Traffic Collector | roleInstance | Yes |
99
-
| Count of flow records processed | Availability | Count | Maximum | Count of number of flow records processed or ingested | roleInstance, ExpressRoute Circuit | Yes |
100
-
101
42
## Circuits metrics
102
43
103
44
### <aname = "circuitbandwidth"></a>Bits In and Out - Metrics across all peerings
Copy file name to clipboardExpand all lines: articles/expressroute/monitor-expressroute.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ If your service uses any non-Azure Monitor based metrics, add the following incl
39
39
40
40
## Analyzing metrics
41
41
42
-
You can analyze metrics for *Azure ExpressRoute* with metrics from other Azure services using metrics explorer by opening **Metrics** from the **Azure Monitor** menu. See [Analyze metrics with Azure Monitor metrics explorer](../azure-monitor/essentials/analyze-metrics.md) for details on using this tool.
42
+
You can analyze metrics for *Azure ExpressRoute* with metrics from other Azure services using metrics explorer by opening **Metrics** from the **Azure Monitor** menu. See [Analyze metrics with Azure Monitor metrics explorer](../azure-monitor/essentials/analyze-metrics.md) for details on using this tool.
43
43
44
44
:::image type="content" source="./media/expressroute-monitoring-metrics-alerts/metrics-page.png" alt-text="Screenshot of the metrics dashboard for ExpressRoute.":::
0 commit comments