Add chart option for cluster-collector to set cache-maxsize if a k8s-cluster generate more than 10000 metrics #27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cluster generate more than 10000 metrics
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA. |
|
@schmidax looks like your GitHub account is not set up properly. Please follow the link from the bot above to fix this. |
|
@robin-checkmk Tanks for the hint, now it is the right email. |
CheckmkCI
pushed a commit
that referenced
this pull request
Oct 15, 2024
This werk introduces the chart option for cluster-collector to set cache-maxsize if a k8s-cluster generates more than 10000 metrics. Closes: #27 Change-Id: If3902a77b8aef64803c75684737dc1b75448dd8d
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there,
For days I have been looking for the reason why the metrics of my large Kubernetes clusters kept getting lost. During my search, I came across the collector option --cache-maxsize, which needs to be increased to solve the problem. This pull request now made it possible to set this value via the helmet chart.
Greetings
schmidax