Story (Required)

ref: https://redhat-internal.slack.com/archives/C050RBV9FJM/p1720615689676759?thread_ts=1720609488.862589&cid=C050RBV9FJM

Console team needs below metrics to expose from PAC side

 
**

1. Number of PipelineRuns associated with Pipelines

• All namespaces
• Particular namespaces    
  • These metrics are already available

2. Maximum duration of a PipelineRuns out of total PipelineRuns

• Particular namespaces
• PipelineRun in a namespace for a pipeline

3. Number of running PipelineRuns for particular namespace ---- Added as part of this story
4. Number of running PipelineRuns for particular namespace particular Pipeline - Added as part of this story

Background (Required)

<Describes the context or background related to this story>

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>

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>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

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