Story (Required)

As a maintainer of Konflux trying to montior tekton health I want to know when pac is deadlocked or suffering from sufficient performance degradation.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

Pac controller has a similar latency histogram metric that we can sample of historical baseline.  Similarly the total requests metric is broken down by status code, so we can use that for success percentages.

Pac watcher has the base knative workqueue depth or latency metrics.

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Aside from the metrics in the background, investigate pac and see if there are certain labels, annotations, etc. that

it always sets, and build a metric that confirms those are set.  This validation is extra credit.

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria  (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met