Jobs and instances
For example, an API server job with four replicated instances:
- job:
- instance 1:
1.2.3.4:5670
- instance 3:
5.6.7.8:5670
- instance 4:
5.6.7.8:5671
- instance 1:
- : The configured job name that the target belongs to.
If either of these labels are already present in the scraped data, the behavior depends on the honor_labels
configuration option. See the scrape configuration documentation for more information.
up{job="<job-name>", instance="<instance-id>"}
: if the instance is healthy, i.e. reachable, or0
if the scrape failed.scrape_duration_seconds{job="<job-name>", instance="<instance-id>"}
: duration of the scrape.scrape_samples_post_metric_relabeling{job="<job-name>", instance="<instance-id>"}
: the number of samples remaining after metric relabeling was applied.- : the approximate number of new series in this scrape. New in v2.10
The up
time series is useful for instance availability monitoring.