Epic Goal

• Add metrics in pipeline service that expose if the service works end to end by running a user like scenario, e.g. running a simple pipeline build. This simple build run on a certain frequency would allow us to know if something is not working from a user’s perspective.  If the build cannot complete in expected time, we shall consider pipeline service down. Pipeline service being down does not necessarily mean that the problem is in the pipeline service, it could be caused by many things(No compute available, network issue, controllers crashing, …) but at least we could, create an alert based on that new metric that will send notifications in konflux-slo-alerts or other alerts channels to ping the on-call engineer. The goal of this alert is to get SRE be notified about possible problems as soon as possible
•  

Why is this important?

• …

Scenarios

1. ...

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):

1. …

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