prometheus-monitoring-stack icon indicating copy to clipboard operation
prometheus-monitoring-stack copied to clipboard

📈 A simple, single-node, Docker-based Prometheus monitoring stack

Results 4 prometheus-monitoring-stack issues
Sort by recently updated
recently updated
newest added

without killing Prometheus docker container if any live update on another containers

prometheus cannot interpret the current config/alert.rules file. `prometheus_1 | level=error caller=manager.go:904 component="rule manager" msg="loading groups failed"` `err="/etc/prometheus/alert.rules: yaml: unmarshal errors:\n line 2: cannot unmarshal !!str `ALERT I...` into rulefmt.RuleGroups"`

docker-compose.yml uses outdated/incompatible service command-line syntax, like `-config.file=/etc/prometheus/prometheus.yml` better: `--config.file=/etc/prometheus/prometheus.yml` or `-collector.procfs=/host/proc` better: `--path.procfs=/host/proc` and some more corrections like the above are needed on Ubuntu18 Linux to start the services.

If my `.env` file contains comments similar to the sample, even the `#` in the middle of the line generates an nginx vhost configuration `Rendering template of # in /etc/nginx/vhosts/#.conf`...