-
Task
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
-
False
-
-
Request type: Feature Request
Reason of urgency: Not urgent
Request info
Team: APPSRE
Tenant: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/app-sre-tenant
Application: qontract-reconcile-master
Details:
PipelineRun Name in metrics Currently, we can get tekton metrics to queries like this https://grafana.app-sre.devshift.net/explore?schemaVersion=1&panes=%7B%2205x%22:%7B%22datasource%22:%22P22466E8E7855F1E0%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22tekton_pipelines_controller_pipelinerun_duration_seconds_count%7Bsource_cluster%3D%5C%22stone-prd-rh01%5C%22,%20namespace%3D%5C%22app-sre-tenant%5C%22%7D%22,%22range%22:true,%22instant%22:true,%22datasource%22:%7B%22type%22:%22prometheus%22,%22uid%22:%22P22466E8E7855F1E0%22%7D,%22editorMode%22:%22code%22,%22legendFormat%22:%22__auto%22%7D%5D,%22range%22:%7B%22from%22:%22now-1h%22,%22to%22:%22now%22%7D%7D%7D&orgId=1 (https://grafana.app-sre.devshift.net/explore?schemaVersion=1&panes=%7B%2205x%22:%7B%22datas[…]om%22:%22now-1h%22,%22to%22:%22now%22%7D%7D%7D&orgId=1) E.g., ```tekton_pipelines_controller_pipelinerun_duration_seconds_count{container="tekton-pipelines-controller",instance="10.128.50.49:9090",job="tekton-pipelines-controller",namespace="app-sre-tenant",pipeline="single-arch-build-pipeline",pod="tekton-pipelines-controller-0",receive="true",service="tekton-pipelines-controller",source_cluster="stone-prd-rh01",source_environment="production-cluster",status="success",tenant_id="0031e8d6-e50a-47ea-aecb-c7e0bd84b3f1"}``` However, that metric does not have PipelineRun name set to know which repo it belongs to. We use a shared pipeline repository for all our pipelines https://github.com/app-sre/shared-pipelines/. The pipelines in here are just being referenced in our PipelineRun objects. Hence, all our PipelineRuns now use the pipeline="single-arch-build-pipeline" and we do not have a way to distinguish the metrics for each build job. Is there a way to have PipelineRun as label too? Or do we have any other way to get metrics for a specific build job that relies on shared pipeline repositories?
- links to