OperationĪll administrative operations including create, update and delete of an ExpressRoute circuit.Īn ExpressRoute circuit was created or updated.įor more information on the schema of Activity Log entries, see Activity Log schema. The following table lists the operations related to ExpressRoute that may be created in the Activity log. For a reference of all Azure Monitor Logs / Log Analytics tables, see the Azure Monitor Log Table Reference. You can query these tables with Log analytics. Azure Monitor Logs tablesĪzure ExpressRoute uses Kusto tables from Azure Monitor Logs. Resource Provider / Type Namespace and link to individual metricsįor reference, see a list of all resource logs category types supported in Azure Monitor. This section lists the types of resource logs you can collect for ExpressRoute. Each ExpressRoute Direct port pair is comprised of two physical links for redundancy, and the supported values are link1 and link2. 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).ĭimension for Express Direct Dimension Name The remote ExpressRoute circuit service key connected using Global Reach.ĭimension for ExpressRoute gateway Dimension Name The supported values are Primary and Secondary. The supported values are Microsoft and Private peering.
Dimension for ExpressRoute circuit Dimension Name Metric dimensionsįor more information on what metric dimensions are, see Multi-dimensional metrics.ĮxpressRoute has the following dimensions associated with its metrics. Using GlobalGlobalReachBitsInPerSecond and GlobalGlobalReachBitsOutPerSecond will only be visible if at least one Global Reach connection is established.
0 kommentar(er)
