mirror of https://github.com/hanzoai/deploy.git synced 2026-10-07 08:44:50 +00:00

Files

T

zeekayandHanzo Dev 446e343a3d cd: annotations are cd.hanzo.ai, API group is apps.hanzo.ai

Two corrections on top of the naming pass, both found by checking the live
cluster rather than the source.

The rename had silently changed the user-facing annotation key from
argocd.argoproj.io/sync-wave to cd.argoproj.io/sync-wave — 63 live
Applications carry the old key, so deploying that would have ignored every
sync-wave and broken fleet deploy ordering. The key is now cd.hanzo.ai/*,
and universe 575650286 moves the ApplicationSet template that stamps it, so
the controller regenerates all 63 consistently.

The API group in code said argoproj.io/v1alpha1 in 157 places while the
cluster has served apps.hanzo.ai/v1alpha1 since 2026-07-23 (the CRDs are
applications.apps.hanzo.ai). Code now matches what is actually served.

The legacy applications.argoproj.io/app-name label had ZERO live users, so it
went with the rest. foo.argoproj.io test fixtures became foo.example.com —
arbitrary test domains should not carry a vendor name.

go build ./... exit 0.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-28 16:32:14 -07:00

782 B

Raw Permalink Blame History

Monitoring

The Hanzo CD Notification controller serves Prometheus metrics on port 9001.

Note

The metrics port can be changed using the --metrics-port flag in cd-notifications-controller deployment.

Metrics

The following metrics are available:

`cd_notifications_deliveries_total`

Number of delivered notifications. Labels:

trigger - trigger name
service - notification service name
succeeded - flag that indicates if notification was successfully sent or failed

`cd_notifications_trigger_eval_total`

Number of trigger evaluations. Labels:

name - trigger name
triggered - flag that indicates if trigger condition returned true or false

Examples

Grafana Dashboard: grafana-dashboard.json

782 B Raw Permalink Blame History