Do not mix tabs and spaces in example YAML config
This commit is contained in:
parent
7a508bd28e
commit
880fb48d77
1 changed files with 2 additions and 2 deletions
|
@ -58,7 +58,7 @@ prometheus_config_scrape_configs_additional:
|
||||||
scrape_timeout: 120s
|
scrape_timeout: 120s
|
||||||
static_configs:
|
static_configs:
|
||||||
- targets:
|
- targets:
|
||||||
- some-host:8080
|
- some-host:8080
|
||||||
|
|
||||||
- job_name: another_job
|
- job_name: another_job
|
||||||
metrics_path: /metrics
|
metrics_path: /metrics
|
||||||
|
@ -66,7 +66,7 @@ prometheus_config_scrape_configs_additional:
|
||||||
scrape_timeout: 120s
|
scrape_timeout: 120s
|
||||||
static_configs:
|
static_configs:
|
||||||
- targets:
|
- targets:
|
||||||
- another-host:8080
|
- another-host:8080
|
||||||
```
|
```
|
||||||
|
|
||||||
If you're scraping others services running in containers over the container network, make sure the Prometheus container is connected to their own network by adjusting `prometheus_container_additional_networks` as demonstrated above for [Integrating with Prometheus Node Exporter](#integrating-with-prometheus-node-exporter).
|
If you're scraping others services running in containers over the container network, make sure the Prometheus container is connected to their own network by adjusting `prometheus_container_additional_networks` as demonstrated above for [Integrating with Prometheus Node Exporter](#integrating-with-prometheus-node-exporter).
|
||||||
|
|
Loading…
Add table
Reference in a new issue