Feature request: Add Syslog monitoring?

geerlingguy / internet-pi

Raspberry Pi config for all things Internet.

MIT License

4.3k stars 448 forks source link

Feature request: Add Syslog monitoring? #369

Closed scottharman closed 2 months ago

scottharman commented 2 years ago

Hi guys - if my router state changes (due to a resync or reboot for example) is there a way to monitor this trough the existing prometheus image, then trigger a new speed test and ping test immediately?

More accurately - that's what I want to do, but is there a better/more sane way to achieve this? Cheers

martinbrose commented 2 years ago

I would think you might need something like this to expose the syslog to Prometheus:

https://github.com/brandond/syslog_ng_exporter

Including some additional config in Prometheus.

Not sure how you would then trigger a new speedtest and ping in the corresponding containers.

martinbrose commented 2 years ago

One way would be through Prometheus alert manager.

https://github.com/prometheus/alertmanager/issues/2046

And use docker exec to trigger a new speedtest and ping in the respective containers.

scottharman commented 2 years ago

I'll try that - thank you!

martinbrose commented 2 years ago

Maybe it's as easy as monitoring the pings in Alertmanager and when a couple fail, then trigger another collection of metrics collections in Prometheus after a minute?

Don't think you'll need the docker exec I mentioned. The whole Prometheus structure is a pull reporting structure.

stale[bot] commented 2 years ago

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

stale[bot] commented 1 year ago

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

stale[bot] commented 1 year ago

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

github-actions[bot] commented 4 months ago

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

github-actions[bot] commented 2 months ago

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.