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

feat: restore k8s.replicaset.* metrics by keeping only non-zero values #252

Merged
merged 1 commit into from
Feb 3, 2025

Conversation

mmanciop
Copy link
Member

No description provided.

@mmanciop mmanciop requested a review from basti1302 January 31, 2025 20:32
k8s.replicaset.available:
enabled: false
enabled: true
Copy link
Member

Choose a reason for hiding this comment

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

nitpick: there is no need to set them to true explicitly, we should just remove the four lines 100-103 entirely, as these two metrics are enabled by default.

Copy link
Member

Choose a reason for hiding this comment

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

fixed

Copy link
Member

@basti1302 basti1302 left a comment

Choose a reason for hiding this comment

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

LGTM in general. We should remove the k8s_cluster metrics config for the two metrics in question and use the fact that they are enabled by default though.

…ero values

This removes noisy replicaset metrics while keeping the ones that
actually have value. By default, Kubernetes keeps a history of 10
replicasets for each deployment, collecting metrics about all of them
leads to a lot of metric datapoints with no value. Removing zero-value
datapoints makes sure the backend knows about the actual active
replicaset (with desired > 0).
Copy link

sonarqubecloud bot commented Feb 3, 2025

@basti1302 basti1302 merged commit 1619918 into main Feb 3, 2025
11 checks passed
@basti1302 basti1302 deleted the k8s-noisy-metrics branch February 3, 2025 07:59
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.

2 participants