Epic Goal

Goal of this epic to identify and execute a clear plan for Pipelines Service Exporter

Why is this important?

• …
  https://redhat-internal.slack.com/archives/C02CTEB3MMF/p1763572779191209

As discussed in Pipelines Architecture call conversations (inputs from jkhelildiagrawavdemeest we need to assess the set of metrics proposed by the service exporter and determine whether:

These metrics can be derived using PromQL queries from existing metrics already exposed by Tekton Pipelines controllers, OR

We need to implement a new standalone metrics controller to export additional metrics without adding load to the Pipeline Controller.

There is upstream context indicating a prior experimental metrics exporter and ongoing discussions in Tekton community regarding splitting metrics-related logic into a dedicated controller. This work needs to be evaluated to align with upstream plans and Konflux observability requirements.

We also need to assess the impact of Census to Telemetry migration for this repository as well.

Scenarios

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

Upstream community issue:
https://github.com/tektoncd/community/issues/1076

Tekton Pipelines issue:
https://github.com/tektoncd/pipeline/issues/7373

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment