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
{{ message }}
This repository was archived by the owner on Aug 31, 2022. It is now read-only.
It is essential to get real run-time metrics to properly integrate kubernetes-event-exporter into a large scale architecture. At a minimum the following provide enough data to get a strong signal for service health:
if the event exporter is up
How many events are being received
How many errors are coming from the watcher
How many errors are coming from the sender
Having these metrics allows us to deploy this on a large scale and have automation determine if there are any problems.
I've got a PR in testing now that exposes these with the standard Prometheus tooling.
Please let me know if there are any problems or concerns, or if you are a user of kubernetes-event-exporter and are interested in seeing this functionality.
It is essential to get real run-time metrics to properly integrate kubernetes-event-exporter into a large scale architecture. At a minimum the following provide enough data to get a strong signal for service health:
Having these metrics allows us to deploy this on a large scale and have automation determine if there are any problems.
I've got a PR in testing now that exposes these with the standard Prometheus tooling.
Please let me know if there are any problems or concerns, or if you are a user of kubernetes-event-exporter and are interested in seeing this functionality.