![]() ![]() # If honor_labels is set to "true", label conflicts are resolved by keeping label # labels, and labels generated by service discovery implementations). # 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. # histogram (has no effect without -enable-feature=native-histograms). # Whether to scrape a classic histogram that is also exposed as a native # 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 # Storage related settings that are runtime reloadable.Ī scrape_config section specifies a set of targets and parameters describing how # Settings related to the remote read feature. # Settings related to the remote write feature. # Alerting specifies settings related to the Alertmanager. # all matching files and appended to the list of scrape configs. # Scrape config files specifies a list of globs. This is an experimental feature, this behaviour could # relabeling, Prometheus will mark the targets as failed without scraping them. If more than this number of targets are present after target # Per-scrape config limit on number of unique targets that will be # If a label value is longer than this number post metric-relabeling, the # Per-scrape limit on length of labels value that will be accepted for a sample. # If a label name is longer than this number post metric-relabeling, the entire # Per-scrape limit on length of labels name that will be accepted for a sample. # entire scrape will be treated as failed. # more than this number of labels are present post metric-relabeling, the ![]() # Per-scrape limit on number of labels that will be accepted for a sample. # the entire scrape will be treated as failed. # If more than this number of samples are present after metric relabeling # Per-scrape limit on number of scraped samples that will be accepted. # This is an experimental feature, this behaviour could # An uncompressed response body larger than this many bytes will cause the # 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |