Skip to content

[COR-923] Register missing metrics with controller-runtime registry#595

Draft
eddiebarth1 wants to merge 1 commit intomainfrom
eduardobarth/cor-923-fix-missing-picchu-datadog-metrics
Draft

[COR-923] Register missing metrics with controller-runtime registry#595
eddiebarth1 wants to merge 1 commit intomainfrom
eduardobarth/cor-923-fix-missing-picchu-datadog-metrics

Conversation

@eddiebarth1
Copy link
Contributor

Summary

  • revisionFailedGauge (picchu_revision_failed) and mirrorFailureCounter (picchu_mirror_failure_counter) were only registered via promauto (global Prometheus registry) but not with the controller-runtime metrics.Registry
  • Since controller-runtime serves /metrics from its own registry, these two metrics were absent from the endpoint
  • Added metrics.Registry.MustRegister() call in RevisionReconciler.SetupWithManager() to match the pattern already used in ReleaseManagerReconciler.SetupWithManager()

Test plan

  • Verify build passes (go build ./...)
  • Verify go vet passes
  • After deploy, confirm picchu_revision_failed and picchu_mirror_failure_counter appear at :8383/metrics
  • Confirm no panic from double-registration (promauto uses default registry, MustRegister uses controller-runtime registry — they are separate)

Companion PR in mono: will link after creation

🤖 Generated with Claude Code

revisionFailedGauge and mirrorFailureCounter were only registered via
promauto (global Prometheus registry) but not with the controller-runtime
metrics.Registry, so they were absent from the /metrics endpoint.

COR-923

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant