Common Labels¶

Telemetruum Labels¶

Following labels are available in all metrics that are generated or scraped by Telemetruum and helps to identify on which node the metric refers to. They can be used to correlate (join) different metrics.

Name	Description	Source
`icos_controller_id`	A unique identifier for the ICOS Controller.	This is manually specified in the Telemetruum Hub instances and autoamtically added to each metric by Telemetruum.
`icos_agent_id`	A unique identifier for the ICOS Agent.	This is manually specified in the Telemetruum Agent instances and automatically added to each metric by Telemetruum.
`icos_cluster_id`	A unique identifier assigned by Telemetruum to the cluster	In Kubernetes, it is the the id of the `default` namespace In Docker, it is the `icos_host_id`
`icos_host_id`	A unique identifier assigned by Telemetruum to the host.	See Host Id section
`icos_host_name`	A unique identifier assigned by Telemetruum to the host.	It is built merging the host id and the hostname in this way: `<first_8_characters_of_host_id>:<hostname>`

System Labels¶

Following labels are added by the underlying technologies used by Telemetruum (Prometheus, Open Telemetry, Thanos). In general, it is not recommended to rely on them because we cannot control them and might be not always available in all metrics.

Name	Description	Source
`k8s_*`	Kubernetes information about the pod that scraped the metric. These labels are available only for metrics generated in a Kubernetes environment. For this reason, it is discouraged to rely on them for getting information on generic ICOS nodes (that can also be Docker).
`instance`
`job`
`net_host_name`
`net_host_port`
`receive`
`server_address`
`server_port`
`server_instance_id`
`server_name`
`tenant_id`
`url_scheme`
`http_scheme`