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

Introduce Prometheus gauge metrics for IP target configuration values #456

Open
tzifudzi opened this issue Aug 23, 2024 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@tzifudzi
Copy link
Contributor

What would you like to be enhanced?

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.

@tzifudzi tzifudzi added the enhancement New feature or request label Aug 23, 2024
@tzifudzi
Copy link
Contributor Author

Created this issue as a follow up change to PR #443. I am willing to take up this task as a fast follow up after the referenced PR is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant