Skip to content

Add prometheus label whitelisting #1981

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

Closed
wants to merge 1 commit into from

Conversation

dashpole
Copy link
Collaborator

Prometheus best practices state Do not use labels to store dimensions with high cardinality (many different label values), such as user IDs, email addresses, or other unbounded sets of values.. We should encourage users to follow this by allowing label whitelisting. This is initially only for prometheus, but flags are intentionally non-specific to allow for other storage plugins to make use of this as well. The default behavior is unchanged, as --enforce_storage_label_whitelist is disabled by default.

This PR adds two new flags:
enforce_storage_label_whitelist, which turns on the whitelisting, and
label_whitelist, which is the set of labels allowed.

Related: #1730
The daemonset (#1979) makes use of these flags so prometheus-to-sd doesn't exceed its label limit.

@dashpole
Copy link
Collaborator Author

also related #1951

@dashpole
Copy link
Collaborator Author

dashpole commented Jul 3, 2018

closing in favor of #1984

@dashpole dashpole closed this Jul 3, 2018
@dashpole dashpole deleted the filter_labels branch July 20, 2018 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants