# server-side ("job" and "instance" labels, manually configured target # already present in scraped data and labels that Prometheus would attach # honor_labels controls how Prometheus handles conflicts between labels that are # The HTTP resource path on which to fetch metrics from targets. # Per-scrape timeout when scraping this job. # How frequently to scrape targets from this job. # The job name assigned to scraped metrics by default. Targets may be statically configured via the static_configs parameter orĭynamically discovered using one of the supported service-discovery mechanisms.Īdditionally, relabel_configs allow advanced modifications to any In advanced configurations, this may change. In the general case, one scrape configuration specifies a single # Settings related to the remote read feature.Ī scrape_config section specifies a set of targets and parameters describing how # Settings related to the remote write feature. # Alerting specifies settings related to the Alertmanager. # Reloading the configuration will reopen the file. # File to which PromQL queries are logged. # external systems (federation, remote storage, Alertmanager). # The labels to add to any time series or alerts when communicating with # How long until a scrape request times out. # How frequently to scrape targets by default. They also serve as defaults for other configuration sections. The global configuration specifies parameters that are valid in all other configurationĬontexts. The other placeholders are specified separately.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |