Close CFR gap: ArgoCD event integration for pal-e-deployments #6

New issue

Closed

opened 2026-05-29 12:05:59 +00:00 by ldraney · 1 comment

ldraney commented

2026-05-29 12:05:59 +00:00

Owner

Type

Feature

Lineage

Standalone — identified as measurement gap in DORA framework.

Repo

ldraney/pal-e-dora-exporter

User Story

As a platform operator
I want Tier 1 DORA composite in Grafana
So that I know if production pipelines are healthy without digging

Context

pal-e-deployments deploys via ArgoCD auto-sync, bypassing Woodpecker entirely. The exporter has no visibility into sync success/failure. Options: ArgoCD notifications webhook to exporter, or leverage ArgoCD's own Prometheus metrics (argocd_app_sync_total) if already exported.

File Targets

Files the agent should modify or create:

src/collectors/argocd.py in pal-e-dora-exporter — new collector (if webhook approach)
Or: Grafana dashboard queries referencing ArgoCD metrics directly (if ArgoCD already exports to Prometheus)

Acceptance Criteria

pal-e-deployments sync events are captured as deployments
dora_deployments_total{repo="pal-e-deployments"} reflects ArgoCD sync outcomes
CFR for pal-e-deployments is measurable in Grafana

Test Expectations

Integration: push a Kustomize change and verify deployment metric increments

Constraints

Evaluate whether ArgoCD already exports Prometheus metrics before building a new collector
Minimal changes to ArgoCD configuration preferred

Checklist

PR opened
Tests pass
No unrelated changes

dora-metrics — project this affects

### Type Feature ### Lineage Standalone — identified as measurement gap in DORA framework. ### Repo `ldraney/pal-e-dora-exporter` ### User Story As a platform operator I want Tier 1 DORA composite in Grafana So that I know if production pipelines are healthy without digging ### Context pal-e-deployments deploys via ArgoCD auto-sync, bypassing Woodpecker entirely. The exporter has no visibility into sync success/failure. Options: ArgoCD notifications webhook to exporter, or leverage ArgoCD's own Prometheus metrics (`argocd_app_sync_total`) if already exported. ### File Targets Files the agent should modify or create: - `src/collectors/argocd.py` in pal-e-dora-exporter — new collector (if webhook approach) - Or: Grafana dashboard queries referencing ArgoCD metrics directly (if ArgoCD already exports to Prometheus) ### Acceptance Criteria - [ ] pal-e-deployments sync events are captured as deployments - [ ] `dora_deployments_total{repo="pal-e-deployments"}` reflects ArgoCD sync outcomes - [ ] CFR for pal-e-deployments is measurable in Grafana ### Test Expectations - [ ] Integration: push a Kustomize change and verify deployment metric increments ### Constraints - Evaluate whether ArgoCD already exports Prometheus metrics before building a new collector - Minimal changes to ArgoCD configuration preferred ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `dora-metrics` — project this affects