Story (Required)

Scope of this story is to clearly document the list of all available metrics for every component both knative as well as the component specific metric. The reason why we need to capture the knative  metric as well is that every component have their own service domain configured and a few do not have any service domain name. We also need to capture the labels associated to the metric. 

Validate the following:
1. What is the port for metrics service of each component. Please note some components can have more than one service - like pipelines have - webhook, controller, resolver.

2. Do we have service monitor properly configured and are the upstream and downstream docs properly validated.

This will be the reference point for evaluating the communication strategy to customers in terms what breaks with the changes specific to OpenTelemetry.

It would be great to capture the possible IMpact for Konflux and performance team along with some grafana screenshots / alerts for reference.

Background (Required)

_This was identified as a mandatory pre-work for - https://issues.redhat.com/browse/SRVKP-8534_

Out of scope

No code changes or fixes are required is anything broken. It is expected to be captured as a Gap. 

Approach (Required)

Assess codebase, expose metrics endpoint in local and capture. DO NOT rely on existing docs to baseline this.

Dependencies

None

Acceptance Criteria (Mandatory)

• Document is clear and captures all details across all components of Tekton

Done Checklist

• Acceptance criteria are met