-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
TaskRun/PipelineRuns that are failed on some reasons can't be recored in Metrics #5866
Comments
It would be great if we have e2e test on metrics to cover the case described in this issue. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Because recording metrics --
durationAndCountMetrics
-- is only called inreconcile()
, taskruns that failed/finished before callingreconcile()
won't be recorded in metrics.Expected Behavior
Metrics should take the following
TaskRuns
into accountSimilarly to
PipelineRun
s that failed before calling reconcile() should also be included in metrics.Actual Behavior
TaskRun
s andPipelineRun
s that failed before callingreconcile()
won't be counted.Steps to Reproduce the Problem
WIP
The text was updated successfully, but these errors were encountered: