-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
Pipelines 1.16.0
-
False
-
None
-
False
-
-
Description of problem:
OpenShift Pipelines does not expose any telemetry for its task/pipeline resolvers. This makes it difficult for cluster administrators to monitor Tekton's performance and diagnose issues specific to resolving remote pipeline/task definitions.
Workaround: None
Prerequisites (if any, like setup, operators/versions):
OpenShift Pipelines 1.16
Steps to Reproduce
- Deploy OpenShift Pipelines with in-cluster monitoring enabled.
- Attempt to construct a query or graph using OpenShift's monitoring stack
Actual results:
No telemetry exists for the resolver
Expected results:
A "resolver latency" metric and/or Histogram that allows a cluster admin to observe success/failure ratios, trends over time to "resolve" a task/pipeline, etc. As an end goal, a cluster admin/SRE should be able to identify that pipelines are failing at the task/pipeline resolution phase and take corrective action.
Reproducibility (Always/Intermittent/Only Once):
Always
Acceptance criteria:
Definition of Done: