-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add the "--opt-in-metrics" argument to the CLI to allow for opt-in metrics #1643
Add the "--opt-in-metrics" argument to the CLI to allow for opt-in metrics #1643
Conversation
…t-in metric family (kubernetes#1574)
I noticed the CI checks and will resolve them this evening! |
f8d3b74
to
dab4a39
Compare
8a95d3e
to
df1e058
Compare
Nice work! /hold for @mrueg to take another look |
…ly from the store (kubernetes#1574)
df1e058
to
da04a73
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fpetkovski, mrueg, Serializator The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
It introduces a way of defining metrics as "opt-in", meaning the end-user needs to specifically specify that metrics which are marked as "opt-in" are to be exposed by the store.
--opt-in-metrics
is used to specify which opt-in metrics to expose from the store. It follows the same notation as the--metric-allowlist
and--metric-denylist
arguments.How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
It does not directly change or affect the cardinality of existing metrics.
Which issue(s) this PR fixes:
Fixes #1574