GeezerVison

Summary by CodeRabbit

• New Features
  • Cluster metrics now include sensor and collector version information. The sensor version is reported from cluster status, while the collector version is reported from collector health information. These details help make the versions associated with cluster metrics visible.

LazyLabels now provides sensor and collector version labels. The sensor version comes from cluster status. The collector version comes from collector health information.

Changes: Cluster version labels

Layer / File(s)	Summary
Add version label getters central/metrics/custom/clusters/labels.go	LazyLabels gains getters for the sensor version from cluster status and the collector version from collector health information.

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Feature

Suggested reviewers: porridge

Merge Risk: Minimal · up to 0574e

The change adds sensor and collector version labels to the cluster info metric, and no concrete runtime risk was found. Shorten the PR title to at most 70 characters so the title check passes.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title names the main change: adding SensorVersion and CollectorVersion labels to the cluster info metric. The raw summary says LazyLabels gains these two labels, sourced from ClusterStatus sensor …
Description check		The description fills the main Description section with a clear explanation of the change. It names the metric, the two new labels, their sources, and an example PromQL query. It also lists build and …
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the main change: adding SensorVersion and CollectorVersion labels to the cluster info metric. The raw summary says LazyLabels gains these two labels, sourced from ClusterStatus sensor version and collector health info version. The title is specific, follows conventional commit form, and is one sentence. It is 83 characters, which is acceptable.

Full details: Description check

Explanation

The description fills the main Description section with a clear explanation of the change. It names the metric, the two new labels, their sources, and an example PromQL query. It also lists build and test results. The template's checklist sections (CHANGELOG or documentation status, production readiness or feature flag, and the automated testing checkboxes) are not ticked or marked. The author gives no explicit statement on whether a CHANGELOG entry or user documentation is needed, and the description does not say whether the new labels are GA or feature-gated. The 'How I validated' section gives build and test commands but no runtime validation of the metric output. The description also contains an 'AI-generated. Review for accuracy.' footer and a 'Chai persona' line that are not part of the template.

Resolution

Optionally tick or explain the user-facing documentation items (CHANGELOG.md and documentation PR), state whether the change is GA or behind a feature flag, and indicate which automated tests were added or modified. Consider adding a short runtime check, such as scraped metric output, to the validation section. Remove the stray 'Chai persona' line and the AI-generated footer.

@@            Coverage Diff             @@
##           master   #24035      +/-   ##
==========================================
- Coverage   52.89%   52.87%   -0.03%     
==========================================
  Files        2755     2755              
  Lines      175277   175277              
==========================================
- Hits        92718    92673      -45     
- Misses      74488    74521      +33     
- Partials     8071     8083      +12     

Flags with carried forward coverage won't be shown. Click here to find out more.

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.