Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Add Syslog monitoring? #369

Open
scottharman opened this issue Mar 31, 2022 · 8 comments
Open

Feature request: Add Syslog monitoring? #369

scottharman opened this issue Mar 31, 2022 · 8 comments
Labels

Comments

@scottharman
Copy link

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
Copy link
Contributor

martinbrose commented Apr 1, 2022

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
Copy link
Contributor

martinbrose commented Apr 1, 2022

One way would be through Prometheus alert manager.

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

@scottharman
Copy link
Author

I'll try that - thank you!

@martinbrose
Copy link
Contributor

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
Copy link

stale bot commented Jul 31, 2022

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.

1 similar comment
@stale
Copy link

stale bot commented Nov 1, 2022

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 stale bot added the stale label Nov 1, 2022
@stale
Copy link

stale bot commented Dec 24, 2022

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 github-actions bot removed the stale label Sep 11, 2023
Copy link

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 github-actions bot added the stale label May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants