1 # Sample config for Prometheus.
4 # Attach these labels to any time series or alerts when communicating with
5 # external systems (federation, remote storage, Alertmanager).
9 # Alertmanager configuration
13 - targets: ['localhost:9093']
15 # Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
17 - /etc/prometheus/rules/*.yml
19 # - "second_rules.yml"
21 # A scrape configuration containing exactly one endpoint to scrape:
22 # Here it's Prometheus itself.
24 # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
25 - job_name: 'prometheus'
27 # metrics_path defaults to '/metrics'
28 # scheme defaults to 'http'.
31 - targets: ['localhost:9090']
32 - job_name: 'alertmanager'
34 - targets: ['localhost:9093']
39 password_file: /etc/prometheus-pass
42 - /etc/prometheus/file_sd/node.yml
47 password_file: /etc/prometheus-pass
50 - /etc/prometheus/file_sd/tlsnode.yml