internet-pi icon indicating copy to clipboard operation
internet-pi copied to clipboard

Published 20 hours ago • verified publisher icon geerlingguy

Feature request: Add Syslog monitoring?

Open scottharman opened this issue 3 years ago • 8 comments

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

scottharman avatar Mar 31 '22 22:03 scottharman

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 avatar Apr 01 '22 16:04 martinbrose

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.

martinbrose avatar Apr 01 '22 16:04 martinbrose

I'll try that - thank you!

scottharman avatar Apr 04 '22 01:04 scottharman

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.

martinbrose avatar Apr 28 '22 10:04 martinbrose

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] avatar Jul 31 '22 22:07 stale[bot]

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] avatar Nov 01 '22 15:11 stale[bot]

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.

stale[bot] avatar Dec 24 '22 01:12 stale[bot]

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] avatar May 27 '24 21:05 github-actions[bot]