Skip to content

Comments

fix: order-dependent metric loss from header dedupe#2866

Open
jfremy-openai wants to merge 1 commit intokubernetes:mainfrom
jfremy-openai:fix-duplicate-header-bugs
Open

fix: order-dependent metric loss from header dedupe#2866
jfremy-openai wants to merge 1 commit intokubernetes:mainfrom
jfremy-openai:fix-duplicate-header-bugs

Conversation

@jfremy-openai
Copy link

What this PR does / why we need it:
Custom resource metrics could disappear depending on metric declaration order when consecutive duplicate headers were sanitized. The old SanitizeHeaders implementation removed duplicate header entries from the header slice, but metric family byte slices remained indexed at their original positions. WriteAll zips headers and families by index, so deleting headers caused index drift and could skip later metric families entirely.

This was especially visible when one duplicate family emitted no samples (e.g. missing nested paths), but the root cause is header/family misalignment and can occur even without empty families.

Fix: preserve positional alignment by blanking duplicate/empty headers instead of removing them. WriteAll already skips empty headers naturally, so output remains deduplicated while family indices stay stable.

Tests: add two regressions in metrics_writer_test

  • duplicate header + empty middle family still preserves later family output
  • duplicate headers without empty families still preserve later family output
    Also update TestSanitizeHeaders expectations for index-preserving blanking behavior.

How does this change affect the cardinality of KSM: does not change cardinality

Custom resource metrics could disappear depending on metric declaration order when consecutive duplicate headers were sanitized. The old SanitizeHeaders implementation removed duplicate header entries from the header slice, but metric family byte slices remained indexed at their original positions. WriteAll zips headers and families by index, so deleting headers caused index drift and could skip later metric families entirely.

This was especially visible when one duplicate family emitted no samples (e.g. missing nested paths), but the root cause is header/family misalignment and can occur even without empty families.

Fix: preserve positional alignment by blanking duplicate/empty headers instead of removing them. WriteAll already skips empty headers naturally, so output remains deduplicated while family indices stay stable.

Tests: add two regressions in metrics_writer_test

- duplicate header + empty middle family still preserves later family output

- duplicate headers without empty families still preserve later family output

Also update TestSanitizeHeaders expectations for index-preserving blanking behavior.
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 5, 2026

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: jfremy-openai / name: Jean-Francois Remy (79cc990)

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 5, 2026
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot
Copy link
Contributor

Welcome @jfremy-openai!

It looks like this is your first PR to kubernetes/kube-state-metrics 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kube-state-metrics has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jfremy-openai
Once this PR has been reviewed and has the lgtm label, please assign catherinef-dev for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Feb 5, 2026
@github-project-automation github-project-automation bot moved this to Needs Triage in SIG Instrumentation Feb 5, 2026
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 5, 2026
@jfremy-openai
Copy link
Author

/easycla

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Feb 9, 2026
@jfremy-openai jfremy-openai changed the title Fix order-dependent metric loss from header dedup index drift Fix: order-dependent metric loss from header dedupe Feb 10, 2026
@jfremy-openai jfremy-openai changed the title Fix: order-dependent metric loss from header dedupe fix: order-dependent metric loss from header dedupe Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

2 participants