bcgov / bcgov/citz-imb-sre-tooling

Define Expections

Open
#3 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## What do we need?

- Status (health/readiness/etc.)
- resource metrics (link to sysdig dashboard)

## What do we want?

- Last deployment timestamp/Image per environment
- Deployed Image tag (and recent 5 with timestamps?)
- Deployment result (success, partial, fail)
- Deployment frequency for that specific product
- Lead time for changes (since the pipeline start to when the deployment is finished)
- Application Deployment Count (per product)
- Share reporting to POs on their products

### Pipeline (CI/GitHub)

- Image Builds
- Status (success, failure, in-progress)
- Trigger type (manual, commit)
- Triggered by (user)

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or implementation entry points are named in the issue. Start by clarifying the scope and success criteria for status, deployment, resource metrics, and CI/GitHub reporting; done would be an agreed, implementable specification for these expectations.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
ci-cd, devops, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.