Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

metrics/features: remove reporting metrics' defaults by default #36298

Merged
merged 3 commits into from
Dec 3, 2024

Conversation

aanm
Copy link
Member

@aanm aanm commented Dec 2, 2024

Having all metrics defaults can cause certain cardinality issue for
production clusters. Since the hive framework does not yet provides a
way to pass a flag to enable, at runtime, the metrics defaults, we need
to use a environment variable. Since, enabling defaults are not actually
intended to be used by users, it's safe to reasonable to have this
option to only be configurable by an environment variable.

@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Dec 2, 2024
@aanm
Copy link
Member Author

aanm commented Dec 2, 2024

/test

@aanm aanm force-pushed the pr/remove-defaults-from-features branch from e9a6fe2 to bd8cd18 Compare December 2, 2024 16:13
@aanm
Copy link
Member Author

aanm commented Dec 2, 2024

/test

@aanm aanm force-pushed the pr/remove-defaults-from-features branch from bd8cd18 to 8509ff6 Compare December 2, 2024 17:11
@aanm
Copy link
Member Author

aanm commented Dec 2, 2024

/test

aanm added 3 commits December 2, 2024 23:03
Having all metrics defaults can cause certain cardinality issue for
production clusters. Since the hive framework does not yet provides a
way to pass a flag to enable, at runtime, the metrics defaults, we need
to use a environment variable. Since, enabling defaults are not actually
intended to be used by users, it's safe to reasonable to have this
option to only be configurable by an environment variable.

Signed-off-by: André Martins <andre@cilium.io>
When running in our CI we are interested to get to know all possible
defaults of the feature metrics, this we should be running then with the
defaults set.

Signed-off-by: André Martins <andre@cilium.io>
The job_name needs to be defined on the workflows as we use it to create
the file with all features that were detected.

Signed-off-by: André Martins <andre@cilium.io>
@aanm aanm force-pushed the pr/remove-defaults-from-features branch from 8509ff6 to 76b8e13 Compare December 2, 2024 22:04
@aanm aanm changed the title Pr/remove defaults from features metrics/features: remove reporting metrics' defaults by default Dec 2, 2024
@aanm aanm added release-note/bug This PR fixes an issue in a previous release of Cilium. area/metrics Impacts statistics / metrics gathering, eg via Prometheus. labels Dec 2, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Dec 2, 2024
@aanm
Copy link
Member Author

aanm commented Dec 2, 2024

/test

@aanm aanm marked this pull request as ready for review December 2, 2024 22:05
@aanm aanm requested review from a team as code owners December 2, 2024 22:05
@aanm aanm requested review from nebril, derailed and brlbil December 2, 2024 22:05
@aanm aanm enabled auto-merge December 2, 2024 22:06
Copy link
Contributor

@derailed derailed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aanm Nice work!

pkg/metrics/features/cell.go Show resolved Hide resolved
@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Dec 3, 2024
@aanm aanm added this pull request to the merge queue Dec 3, 2024
Merged via the queue into main with commit 8da6f36 Dec 3, 2024
298 checks passed
@aanm aanm deleted the pr/remove-defaults-from-features branch December 3, 2024 19:31
@aanm aanm added backport-pending/1.14 The backport for Cilium 1.14.x for this PR is in progress. backport-pending/1.15 The backport for Cilium 1.15.x for this PR is in progress. backport-pending/1.16 The backport for Cilium 1.16.x for this PR is in progress. labels Dec 16, 2024
@github-actions github-actions bot added backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. and removed backport-pending/1.16 The backport for Cilium 1.16.x for this PR is in progress. labels Dec 16, 2024
@aanm aanm mentioned this pull request Dec 17, 2024
14 tasks
@github-actions github-actions bot added backport-done/1.14 The backport for Cilium 1.14.x for this PR is done. and removed backport-pending/1.14 The backport for Cilium 1.14.x for this PR is in progress. labels Dec 18, 2024
@github-actions github-actions bot added backport-done/1.15 The backport for Cilium 1.15.x for this PR is done. and removed backport-pending/1.15 The backport for Cilium 1.15.x for this PR is in progress. labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/metrics Impacts statistics / metrics gathering, eg via Prometheus. backport-done/1.14 The backport for Cilium 1.14.x for this PR is done. backport-done/1.15 The backport for Cilium 1.15.x for this PR is done. backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/bug This PR fixes an issue in a previous release of Cilium.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants