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

Ensure that the cumulative chaos metrics are not dependent on the presence of chaosengine/chaoseresult resources on the cluster #142

Open
ksatchit opened this issue Jul 27, 2023 · 0 comments
Assignees

Comments

@ksatchit
Copy link
Member

The total run/pass/fail metrics coming from the exporter today are dependent on the presence of the chaosengine and chaosresult resources in the cluster. In other words, they are providing state for the exporter. Upon periodic polling intervals OR upon startup - the exporter scans for these CRs and calculates the metric values exposed over :8080/metrics.

However, with logging integration having been achieved, we no longer plan to keep these CRs on the cluster. They will be auto-cleaned up. This will cause the exporter to throw up incorrect values for these cumulative metrics.

We need alternative state-management. Potential approaches include usage of textfile collectors, querying from control plane (db), or moving to the prometheus push-model.

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

No branches or pull requests

2 participants