You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Sadly I have no know how in C so I will not be able to implement this feature.
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: