[ metrics_path: <path> | default = /metrics ] # honor_labels controls how Prometheus handles conflicts between labels that are # already present in scraped data and labels that Prometheus would attach # server-side ("job" and "instance" labels, manually configured target # labels, and labels generated by service discovery implementations). # # If honor_labels is set to "true", label conflicts are resolved by keeping label # values from the scraped data and ignoring the conflicting server-side labels. # # If honor_labels is set to "false", label conflicts are resolved by renaming # conflicting labels in the scraped data to "exported_<original-label>" (for # example "exported_instance", "exported_job") and then attaching server-side # labels.

# A scrape configuration containing exactly one endpoint to scrape: # Here it's Prometheus itself. scrape_configs: # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config. - job_name: "prometheus" ·  ...

You should now have example targets listening on http://localhost:8080/metrics , http://localhost:8081/metrics , and http://localhost:8082/metrics . Now we will configure Prometheus to scrape these new targets. Let's group all three endpoints into one job called node.

July 16, 2026 - Note: the example below demonstrates overriding defaults for a job; scheme and metrics_path are illustrative. Most exporters use http and the default metrics_path (/metrics). global: scrape_interval: 1m # default scrape interval for jobs that don't override it scrape_timeout: 10s # default scrape timeout scrape_configs: - job_name: "prometheus" static_configs: - targets: ["localhost:9090"] - job_name: "nodes" scrape_interval: 15s # overrides global scrape_interval for this job scrape_timeout: 5s # per-job scrape timeout scheme: https # defaults to http if not set metrics_path: /stats/metrics static_configs: - targets: ["192.168.1.168:9100"]

global: scrape_interval: 15s ... ['localhost:9090'] There are three blocks of configuration in the example configuration file: global, rule_files, and scrape_configs....

January 2, 2025 - Finally, we replace the job, default-namespace-pods, we created in the last section with the kubernetes-job example provided in the Helm chart default values (see below). We do this as before by editing the values.yaml and using helm upgrade. Yes, this is appears mind-boggling complex at first glance; we will dig into this configuration below. - job_name: 'kubernetes-pods' honor_labels: true kubernetes_sd_configs: - role: pod relabel_configs: - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape] action: keep regex: true - source_labels: [__meta_kubernetes_pod_annotation_prom

A full prometheus.yml file can be found at https://github.com/couchbaselabs/cbprometheus_python/blob/master/prometheus/prometheus.yml ... global: scrape_interval: 60s # How frequently to scrape targets by default. scrape_timeout: 10s # How long ...

Example Prometheus configuration (scrape config). GitHub Gist: instantly share code, notes, and snippets.

The global section configures global settings and default values, whereas the scrape_configs section tells Prometheus which targets to scrape.

February 7, 2024 - Here are several types of Prometheus ... alerting configurations. Example Use Case: Setting up Prometheus to monitor a single application or service with straightforward metrics....

global: scrape_interval: 10s external_labels: monitor: 'media_search' scrape_configs: - job_name: 'media_search' scrape_interval: 10s static_configs: - targets: ['localhost:9888', 'localhost:9988', 'localhost:9989'] Having successfully downloaded Prometheus and setup your config.yaml file, you should now be able to run

Many open source projects provide Prometheus exporters so that you can scrape metrics from your application at any given point in time. Typically, the Prometheus metrics collector configuration file specifies how frequently to collect your metrics, known as the scrape_config, plus the remote endpoint and authentication parameters for reliably storing the metrics, available under remote_write.

January 7, 2025 - Sitemap · Open in app · Sign up · Sign in · Get app · Write · Search

http_sd_configs: - url: "http://example.com/prometheus" · - job_name: service-triton · triton_sd_configs: - account: "testAccount" dns_suffix: "triton.example.com" endpoint: "triton.example.com" port: ...

The defaults applied before parsing the respective config sections. ... var ( PrometheusProto ScrapeProtocol = "PrometheusProto" PrometheusText0_0_4 ScrapeProtocol = "PrometheusText0.0.4" PrometheusText1_0_0 ScrapeProtocol = "PrometheusText1.0.0" OpenMetricsText0_0_1 ScrapeProtocol = "OpenMetricsText0.0.1" OpenMetricsText1_0_0 ScrapeProtocol = "OpenMetricsText1.0.0" UTF8NamesHeader string = model.EscapingKey + "=" + model.AllowUTF8 ScrapeProtocolsHeaders = map[ScrapeProtocol]string{ PrometheusProto: "application/vnd.google.protobuf;proto=io.prometheus.client.MetricFamily;encoding=delimited", P

1 month ago - alertmanager: config: alertmanager_yml: | global: templates: - '/etc/alertmanager/templates/*.tmpl' route: group_interval: 5m group_wait: 10s receiver: default-receiver repeat_interval: 3h receivers: - name: default-receiver deployment: replicas: 1 rollingUpdate: maxSurge: 25% maxUnavailable: 25% updateStrategy: Recreate pvc: accessMode: ReadWriteOnce storage: 2Gi storageClassName: global-storage-profile service: port: 80 targetPort: 9093 type: ClusterIP ingress: alertmanager_prefix: /alertmanager/ alertmanagerServicePort: 80 enabled: true prometheus_prefix: / prometheusServicePort: 80 virtual

February 2, 2026 - # prometheus.yml - Consul service discovery scrape_configs: - job_name: 'consul-services' consul_sd_configs: - server: 'consul.example.com:8500' # Optionally filter by datacenter datacenter: 'dc1' # Filter by service tags tags: - 'prometheus' - 'production' # Allow stale results from non-leader Consul nodes (reduces load; default: true) allow_stale: false # Refresh service list interval refresh_interval: 30s relabel_configs: # Use Consul service name as job label - source_labels: [__meta_consul_service] action: replace target_label: job # Add datacenter label - source_labels: [__meta_consul_dc

April 30, 2026 - Used to explicitly specify the ... on the fly. Relabeling can be applied to both goal labels · Example: static_configs: - targets: ["localhost:9100"]...

receivers: - name: "alerta" webhook_configs: - url: 'http://alerta:8080/api/webhooks/prometheus' send_resolved: true http_config: basic_auth: username: admin@alerta.io password: alerta · Example alertmanager.yml receivers section with API Key

September 30, 2025 - The name of the key password1 can be anything as long as it matches the file name in the password_file filepath in the Prometheus scrape config in the next step. The value for the key needs to be base64-encoded. apiVersion: v1 kind: Secret metadata: name: ama-metrics-mtls-secret namespace: kube-system type: Opaque data: password1: <base64-encoded-string> The ama-metrics-mtls-secret secret is mounted on to the ama-metrics pods at the path /etc/prometheus/certs/ and is made available to the Prometheus scraper. The key (password1 in the above example) will be the file name.