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
Currently, the approach to monitor the configuration values of warmIPTarget, minIPTarget, and warmPrefixTarget is to log the values and while this is sufficient, it is not an optimal solution for observability. For example logs can be difficult to search and analyze.
Why is the change needed and what use case will it solve?
By exposing these configuration values as Prometheus gauge metrics, we can provide a more visual and easily accessible way for operators to monitor the state of these values. This might enable better auditing and also better investigation of issues.
Suggestions for the change
Introduce new Prometheus gauge metrics for each of the configuration values (warmIPTarget, minIPTarget, and warmPrefixTarget). These metrics should be updated whenever the corresponding configuration values change, providing real-time visibility into their state.
The text was updated successfully, but these errors were encountered:
What would you like to be enhanced?
Currently, the approach to monitor the configuration values of
warmIPTarget
,minIPTarget
, andwarmPrefixTarget
is to log the values and while this is sufficient, it is not an optimal solution for observability. For example logs can be difficult to search and analyze.Why is the change needed and what use case will it solve?
By exposing these configuration values as Prometheus gauge metrics, we can provide a more visual and easily accessible way for operators to monitor the state of these values. This might enable better auditing and also better investigation of issues.
Suggestions for the change
Introduce new Prometheus gauge metrics for each of the configuration values (
warmIPTarget
,minIPTarget
, andwarmPrefixTarget
). These metrics should be updated whenever the corresponding configuration values change, providing real-time visibility into their state.The text was updated successfully, but these errors were encountered: