-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
custom metrics gc no longer cleans old emitted metrics #11542
Comments
Follow-up from Slack. |
This seems to have the same root cause as #11541, which is due to a regression caused by #11178. Seems like the Will have to check if all of that logic can be moved to post-init without breaking anything. |
cc @astraw99 |
…proj#11542, argoproj#11541 Signed-off-by: Yuan Tang <terrytangyuan@gmail.com>
Fixing in #11553 to revert the commit. |
thank you all for the very quick help and fix with the bug. you're amazing! |
…proj#11542, argoproj#11541 (argoproj#11553) Signed-off-by: Yuan Tang <terrytangyuan@gmail.com> Signed-off-by: Dillen Padhiar <dillen_padhiar@intuit.com>
Pre-requisites
:latest
What happened/what you expected to happen?
After upgrading to v3.4.9 (and latest) custom metrics will no longer get cleaned up after "metricsTTL" time has been reached and will stay exposed at the metrics endpoint endlessly.
e.g. example workflow emits the following metric
argo_workflows_result_task_counter{id="b68baed7-b2a5-4718-bac4-221d559c750f",status="Succeeded",task_name="example-metrics"} 1
which will stay until pod get recreated.downgrade to v3.4.8 without any configuration change leads to expected behaviour of metric no longer being exposed after TTL time has been reached.
workflow-controller-configmap for reference:
Version
v3.4.9, latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: