Skip to content

Stamp build_info and mark reserved-always-zero series as reserved - #64

Merged
Yanujz merged 1 commit into
mainfrom
issue-62-metrics-accuracy
Sep 19, 2026
Merged

Yanujz merged 1 commit into
mainfrom
issue-62-metrics-accuracy

Conversation

@Yanujz

@Yanujz Yanujz commented Sep 19, 2026

Copy link
Copy Markdown
Collaborator

What changes for operators?

/metrics epmon_build_info now carries the release version/commit (was always empty) so dashboards can correlate behavior with builds. README marks the five never-incremented series (plus queue gauges) as reserved-for-future-use instead of actionable — no renames, no removals, names stay compat surface.

Failing-then-passing test

New TestBuildInfo pins the stamped rendering; the wiring gap (main never called SetBuildInfo) is verified live below before merge: boot dev binary, build_info shows empty labels on main code vs dev/unknown with the fix.

Checklist

  • go build ./... && go vet ./... && go test ./... green with -race (metrics + cmd; full suite at merge)
  • gofmt -l . clean
  • OpenAPI updated if API surface changed — N/A
  • No fabricated history — N/A
  • No secrets, tokens, or hosts I don't own in the diff

Fixes #62

Nothing called SetBuildInfo, so /metrics always rendered empty build
labels next to a correctly stamped version subcommand. Wire the package
vars into the registry at boot, pin the rendering with a test, and stop
presenting never-incremented series as actionable alerts in the README.

Fixes #62
@Yanujz
Yanujz merged commit a5079e1 into main Sep 19, 2026
1 check passed
@Yanujz
Yanujz deleted the issue-62-metrics-accuracy branch September 19, 2026 17:39
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.

Stamp epmon_build_info and mark reserved-always-zero series as reserved

1 participant