You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add ability to include reason in count metrics
Adds a configuration flag to enable including the `reason` for a TaskRun or PipelineRun status on their count metrics. This allows for more fine-grained monitoring and alerting of run failures.
Signed-off-by: Marcus Noble <[email protected]>
@@ -40,6 +40,7 @@ A sample config-map has been provided as [config-observability](./../config/conf
40
40
metrics.taskrun.duration-type: "histogram"
41
41
metrics.pipelinerun.level: "pipeline"
42
42
metrics.pipelinerun.duration-type: "histogram"
43
+
metrics.count.enable-reason: "false"
43
44
```
44
45
45
46
Following values are available in the configmap:
@@ -56,6 +57,7 @@ Following values are available in the configmap:
56
57
| metrics.taskrun.duration-type | `lastvalue` | `tekton_pipelines_controller_pipelinerun_taskrun_duration_seconds` and `tekton_pipelines_controller_taskrun_duration_seconds` is of type gauge or lastvalue |
57
58
| metrics.pipelinerun.duration-type | `histogram` | `tekton_pipelines_controller_pipelinerun_duration_seconds` is of type histogram |
58
59
| metrics.pipelinerun.duration-type | `lastvalue` | `tekton_pipelines_controller_pipelinerun_duration_seconds` is of type gauge or lastvalue |
60
+
| metrics.count.enable-reason | `false` | Sets if the `reason` label should be included on count metrics |
59
61
60
62
Histogram value isn't available when pipelinerun or taskrun labels are selected. The Lastvalue or Gauge will be provided. Histogram would serve no purpose because it would generate a single bar. TaskRun and PipelineRun level metrics aren't recommended because they lead to an unbounded cardinality which degrades the observability database.
0 commit comments