-
Notifications
You must be signed in to change notification settings - Fork 545
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
validation: allow more labels for _info metrics by default #10028
Changes from all commits
144b03a
1627c13
8d251da
e721d63
7821dd1
0fbdd0a
0a9d7a7
98501fb
d42265c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -1729,6 +1729,16 @@ The limit protects the system’s stability from potential abuse or mistakes. To | |||||
Invalid series are skipped during the ingestion, and valid series within the same request are ingested. | ||||||
{{< /admonition >}} | ||||||
|
||||||
### err-mimir-max-label-names-per-info-series | ||||||
|
||||||
This non-critical error occurs when Mimir receives a write request that contains an info series with a number of labels that exceeds the configured limit. | ||||||
An info series is a series where the metric name ends in `_info`. | ||||||
The limit protects the system’s stability from potential abuse or mistakes. To configure the limit on a per-tenant basis, use the `-validation.max-label-names-per-info-series` option. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To configure per tenant, you need YAML don't you rather than the flag:
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ack, I'll update this and where I copy pasted from above as well There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. also it becomes There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually there's 10 places where we use There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I certainly wouldn't change existing code as part of this PR. I just don't think it makes sense to refer to a flag, when you have to use YAML per-tenant. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: I think There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The doc uses |
||||||
|
||||||
{{< admonition type="note" >}} | ||||||
Invalid series are skipped during ingestion, and valid series in the same request are ingested. | ||||||
{{< /admonition >}} | ||||||
|
||||||
### err-mimir-max-native-histogram-buckets | ||||||
|
||||||
This non-critical error occurs when Mimir receives a write request that contains a sample that is a native histogram that has too many observation buckets. | ||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is
info series
an abbreviation forinformation series
or is it really just called aninfo series
? If it's an abbreviation, we should spell it out except when using a code-formatted label.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not an abbreviation, these are called info series/metrics everywhere