Update monitoring/docker-compose.yml#44
Conversation
Nodeexporter does not have an access to system network metrics, need to map /proc and make some magic with PID=1
…ker-compose.yml, updated Prometheus alertmanager rules
|
Prometheus container keeps restarting out-of-the box. Error message in logs: Please fix. |
|
I am not sure I understand, there is no lock file in the location you specified: https://github.com/uschtwill/docker_monitoring_logging_alerting/tree/master/storage |
|
Sorry, Prometheus creators have changed user used for Prometheus running (https://prometheus.io/docs/prometheus/2.0/migration/ - section miscelaneous).
|
|
I am pretty sure Prometheus' tsdb is already contained in a volume, no? I am currently not as deeply involved in the specifics, but isn't Prometheus putting the tdsb here? I guess from the remaining two options I prefer 1. Would you amend your PR? |
|
make a config folder in the location of your docker-compose.yml. insert the files prometheus.yml and alert_rules.yml in the config folder. This code worked for me on v2.10 prometheus image |
Nodeexporter does not have an access to system network metrics, need to map /proc and make some magic with PID=1