Guest OS metrics must be collected through one or more agents that run on or as part of the guest operating system. Metrics for the guest operating system (guest OS) that runs in Azure Virtual Machines, Service Fabric, and Cloud Services are not listed here. But when the metric is exported via diagnostic settings, it will be represented as all incoming messages across all queues in the event hub. Metrics with dimensions are exported as flattened single-dimensional metrics, aggregated across dimension values.įor example, the Incoming Messages metric on an event hub can be explored and charted on a per-queue level. Sending multi-dimensional metrics to other locations via diagnostic settings is not currently supported. The column "Exportable via Diagnostic Settings" in the following tables lists which metrics can be exported in this way. All metrics are exportable through the REST API, but some can't be exported through diagnostic settings because of intricacies in the Azure Monitor back end. Using diagnostic settings is the easiest way to route the metrics, but there are some limitations:Įxportability. Event hubs, which is how you get them to non-Microsoft systems.Azure Monitor Logs (and thus Log Analytics).Use diagnostic settings to route platform metrics to:.You can export the platform metrics from the Azure monitor pipeline to other locations in one of two ways: Exporting platform metrics to other locations For a list of services and the resource providers and types that belong to them, see Resource providers for Azure services. The metrics are organized by resource provider and resource type. Other metrics not in this list might be available in the portal or through legacy APIs. To query for and access the list of metrics programmatically, use the api-version. Metrics changed or added after the date at the top of this article might not yet appear in the list. This article is a complete list of all platform (that is, automatically collected) metrics currently available with the consolidated metric pipeline in Azure Monitor.
Grafana internet uptime monitor how to#
Contact the author of this article for details on how to make permanent updates.Īzure Monitor provides several ways to interact with metrics, including charting them in the Azure portal, accessing them through the REST API, or querying them by using PowerShell or the Azure CLI. Any modification made to this list via GitHub might be written over without warning. There, select Host check command as Use the status of the service… and enter Internet connection as its name - the same name you chose as the service name in the previous step.This list is largely auto-generated. Enable Number of positive responses required for OK state and enter 1.Ĭreate another rule that also only applies to the host internet, this time from the Host check command rule set. Enable Alternate address to ping and select Ping all IPv4 addresses there. Configure the rule as follows: Enable Service Description and enter Internet connection. Save the host without service detection.Ĭreate a new rule from the Check hosts with PING (ICMP Echo Request) rule set that only applies to the new host internet (for example, via the Explicit hosts condition, or a matching host tag). Enable the Checkmk Agent data source and set it to No agent. Under Additional IPv4 addresses enter the remaining IP addresses.
![grafana internet uptime monitor grafana internet uptime monitor](https://i.imgur.com/MnIXwhH.png)
Select several computers on the Internet that should normally be reachable via a ping command and note their IP addresses.Ĭreate a new host in Checkmk, for example with the name internet and configure it as follows: For IPv4 Address enter one of the noted IP addresses.