

- #EMCOPY UNABLE TO OPEN THE OBJECT FOR SD SETTING PASSWORD#
- #EMCOPY UNABLE TO OPEN THE OBJECT FOR SD SETTING SERIES#
# password and password_file are mutually exclusive. # Sets the `Authorization` header on every scrape request with the # Configures the protocol scheme used for requests. # If honor_timestamps is set to "false", the timestamps of the metrics exposed # If honor_timestamps is set to "true", the timestamps of the metrics exposed # honor_timestamps controls whether Prometheus respects the timestamps present
#EMCOPY UNABLE TO OPEN THE OBJECT FOR SD SETTING SERIES#
# when a time series does not have a given label yet and are ignored otherwise. In communication with external systems, they are always applied only # Note that any globally configured "external_labels" are unaffected by this # scraping the Pushgateway, where all labels specified in the target should be # Setting honor_labels to "true" is useful for use cases such as federation and # example "exported_instance", "exported_job") and then attaching server-side # conflicting labels in the scraped data to "exported_" (for # If honor_labels is set to "false", label conflicts are resolved by renaming # values from the scraped data and ignoring the conflicting server-side labels. # 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. # 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. : a string which is template-expanded before usage.Supported units: B, KB, MB, GB, TB, PB, EB. : a regular string that is a secret, such as a password.


Prometheus is configured via command-line flags and a configuration file.
