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
This section lists all the automatically collected platform metrics for ExpressRoute. For more information, see a list of [all platform metrics supported in Azure Monitor](../azure-monitor/essentials/metrics-supported.md).
15
+
See [Monitor Azure ExpressRoute](monitor-expressroute.md) for details on the data you can collect for ExpressRoute and how to use it.
20
16
21
-
| Metric Type | Resource Provider / Type Namespace<br/> and link to individual metrics |
> Using *GlobalGlobalReachBitsInPerSecond* and *GlobalGlobalReachBitsOutPerSecond*will only be visible if at least one Global Reach connection is established.
20
+
> Using *GlobalGlobalReachBitsInPerSecond* and *GlobalGlobalReachBitsOutPerSecond*are only visible if at least one Global Reach connection is established.
30
21
>
31
22
32
-
## Metric dimensions
23
+
### Supported metrics for Microsoft.Network/expressRouteCircuits
24
+
25
+
The following table lists the metrics available for the Microsoft.Network/expressRouteCircuits resource type.
### Supported metrics for Microsoft.Network/expressRouteCircuits/peerings
31
+
32
+
The following table lists the metrics available for the Microsoft.Network/expressRouteCircuits/peerings resource type.
33
33
34
-
For more information on what metric dimensions are, see [Multi-dimensional metrics](../azure-monitor/essentials/data-platform-metrics.md#multi-dimensional-metrics).
|**PeeringType**| The type of peering configured. The supported values are Microsoft and Private peering. |
43
-
|**Peering**| The supported values are Primary and Secondary. |
44
-
|**PeeredCircuitSkey**| The remote ExpressRoute circuit service key connected using Global Reach. |
58
+
|:---------------|:------------|
59
+
| PeeringType | The type of peering configured. The supported values are Microsoft and Private peering. |
60
+
| Peering | The supported values are Primary and Secondary. |
61
+
| DeviceRole ||
62
+
| PeeredCircuitSkey | The remote ExpressRoute circuit service key connected using Global Reach. |
45
63
46
-
### Dimension for ExpressRoute gateway
64
+
Dimension for ExpressRoute gateway:
47
65
48
66
| Dimension Name | Description |
49
-
| ------------------- | ----------------- |
50
-
|**roleInstance**| The gateway instance. Each ExpressRoute gateway is comprised of multiple instances, and the supported values are GatewayTenantWork_IN_X (where X is a minimum of 0 and a maximum of the number of gateway instances -1). |
67
+
|:-------------- |:----------- |
68
+
| BgpPeerAddress ||
69
+
| ConnectionName ||
70
+
| direction ||
71
+
| roleInstance | The gateway instance. Each ExpressRoute gateway is comprised of multiple instances, and the supported values are GatewayTenantWork_IN_X (where X is a minimum of 0 and a maximum of the number of gateway instances -1). |
51
72
52
-
### Dimension for Express Direct
73
+
Dimension for Express Direct:
53
74
54
75
| Dimension Name | Description |
55
-
| ------------------- | ----------------- |
56
-
|**Link**| The physical link. Each ExpressRoute Direct port pair is comprised of two physical links for redundancy, and the supported values are link1 and link2. |
76
+
|:---------------|:------------|
77
+
| Lane ||
78
+
| Link | The physical link. Each ExpressRoute Direct port pair is comprised of two physical links for redundancy, and the supported values are link1 and link2. |
Azure ExpressRoute uses Kusto tables from Azure Monitor Logs. You can query these tables with Log analytics. For a reference of all Azure Monitor Logs / Log Analytics tables, see the [Azure Monitor Log Table Reference](/azure/azure-monitor/reference/tables/tables-resourcetype).
The following table lists the operations related to ExpressRoute that may be created in the Activity log.
75
99
@@ -87,16 +111,16 @@ For detailed description of the top-level diagnostic logs schema, see [Supported
87
111
88
112
When reviewing any metrics through Log Analytics, the output will contain the following columns:
89
113
90
-
|**Column**|**Type**|**Description**|
91
-
|---|---|---|
92
-
|TimeGrain|string|PT1M (metric values are pushed every minute)|
93
-
|Count|real|Usually equal to 2 (each MSEE pushes a single metric value every minute)|
94
-
|Minimum|real|The minimum of the two metric values pushed by the two MSEEs|
95
-
|Maximum|real|The maximum of the two metric values pushed by the two MSEEs|
96
-
|Average|real|Equal to (Minimum + Maximum)/2|
97
-
|Total|real|Sum of the two metric values from both MSEEs (the main value to focus on for the metric queried)|
114
+
|Column|Type|Description|
115
+
|:-------|:-----|:------------|
116
+
|TimeGrain|string|PT1M (metric values are pushed every minute)|
117
+
|Count|real|Usually equal to 2 (each MSEE pushes a single metric value every minute)|
118
+
|Minimum|real|The minimum of the two metric values pushed by the two MSEEs|
119
+
|Maximum|real|The maximum of the two metric values pushed by the two MSEEs|
120
+
|Average|real|Equal to (Minimum + Maximum)/2|
121
+
|Total|real|Sum of the two metric values from both MSEEs (the main value to focus on for the metric queried)|
98
122
99
-
## See also
123
+
## Related content
100
124
101
-
- See [Monitoring Azure ExpressRoute](monitor-expressroute.md) for a description of monitoring Azure ExpressRoute.
102
-
- See [Monitoring Azure resources with Azure Monitor](../azure-monitor/essentials/monitor-azure-resource.md) for details on monitoring Azure resources.
125
+
- See [Monitor Azure ExpressRoute](monitor-expressroute.md) for a description of monitoring ExpressRoute.
126
+
- See [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for details on monitoring Azure resources.
0 commit comments