[prometheus-users] How to sense disk read/write errors

Had two users come at me with "why didn't you...?" because of a machine that had disk hardware failures, but no alerts before the device died. They pointed at these messages in the kernel dmesg: > [Wed May 17 06:07:05 2023] nvme nvme3: async event result 00010300 > [Wed May 17 06:07:25 2023] nvme

Re: [prometheus-users] EOF errors waiting on consul_sd_config requests

> which version prometheus, version 2.19.0 (branch: HEAD, revision: 5d7e3e970602c755855340cb190a972cebdd2ebf) go version: go1.14.4 does it go away in a newer version? -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe fr

[prometheus-users] EOF errors waiting on consul_sd_config requests

I have a Prometheus server using consul_sd_config for target discovery. Some services aren't always present, but when they appear I want Prometheus to scrape them. consul_sd_config does this nicely. But it complains a lot. level=error ts=2020-10-06T16:52:58.990Z caller=consul.go:503 component="d