-
-
Notifications
You must be signed in to change notification settings - Fork 730
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
Add keepalived_exporter into the original project #1731
Comments
At https://github.com/prometheus/prometheus/wiki/Default-port-allocations it lists https://github.com/cafebazaar/keepalived-exporter as well as the gen2brain exporter above. However, these are not the sort of exporters that would be implemented from within keepalived itself; the exporters above trigger keepalived to generate files and then parse those files to provide the data to Prometheus. If keepalived were to implement an exporter, it would be more like HAProxy's PROMEX, so that the application directly generates the output for Prometheus. And then should we do something to work with Grafana such as provide some dashboards like RabbitMQ does? I think implementing this is something that someone could helpfully contribute. As a minimum it would be good to start with the framework with a few items exported, ensuring that this includes examples of each data type, and then this could be built upon over time. Of course, this would need to be written in C, since that is the language that keepalived used. |
I would really like to see a prometheus endpoint directly in keepalived. |
Currently, we have only SNMP and script for monitoring.
We cloud use prometheus exporter like many project (Haproxy, postgres, apache, ngnix, etc.)
Maybe the project https://github.com/gen2brain/keepalived_exporter is well-coded and it can be integrated in the original project
The text was updated successfully, but these errors were encountered: