docs: Guide on how to setup UTF-8 mode in Cortex#7439
Conversation
Signed-off-by: Raphael Skuza <rapsku.dev@gmail.com>
| name_validation_scheme: utf8 | ||
| ``` | ||
|
|
||
| ### Impact on Cortex components |
There was a problem hiding this comment.
Since the Distributor is a sub-item, it would be better to increase to the ##.
| ### Impact on Cortex components | |
| ## Impact on Cortex components |
There was a problem hiding this comment.
Typo, thank you for pointing it out
|
@RaphSku |
| * [FEATURE] Ingester: Add experimental active series queried metric. #7173 | ||
| * [FEATURE] Update prometheus Alertmanager version to v0.31.1 and add new integration to IncidentIO and Mattermost. #7092 #7267 | ||
| * [FEATURE] Tenant Federation: Add experimental support for partial responses using the `-tenant-federation.allow-partial-data` flag. When enabled, failures from individual tenants during a federated query are treated as warnings, allowing results from successful tenants to be returned. #7232 | ||
| * [ENHANCEMENT] Docs: Guide on UTF-8 Support in Cortex #7091 |
There was a problem hiding this comment.
I don't think it's necessary to leave it in the changelog.
Signed-off-by: Raphael Skuza <rapsku.dev@gmail.com>
I've added the mentioned components to the guide, thank you for the review. If there is something in particular I should mention about either component, let me know. |
|
@RaphSku
Adding a few short YAML or PromQL snippets based on our tests would perfectly bridge the gap between the configuration and actual usage. |
…tilize UTF-8 support Signed-off-by: Raphael Skuza <rapsku.dev@gmail.com>
|
@SungJin1212 Thank you again for your comment, totally valid to have such a section and a good idea. I have included it in the latest commit. |
| series.1{"test.utf8.metric"="😄"} | ||
| ``` | ||
|
|
||
| Note, that the metric name `series.1` is not valid under the `legacy` validation scheme. It is accepted only when UTF-8 validation is enabled. This is useful when metric or label names contain characters, such as `.`, that are supported by UTF-8 validation but not by the legacy validation scheme. |
There was a problem hiding this comment.
| Note, that the metric name `series.1` is not valid under the `legacy` validation scheme. It is accepted only when UTF-8 validation is enabled. This is useful when metric or label names contain characters, such as `.`, that are supported by UTF-8 validation but not by the legacy validation scheme. | |
| Note that the metric name `series.1` is not valid under the `legacy` validation scheme. It is accepted only when UTF-8 validation is enabled. This is useful when metric or label names contain characters, such as `.`, that are supported by UTF-8 validation but not by the legacy validation scheme. |
Signed-off-by: Raphael Skuza <rapsku.dev@gmail.com>
2 participants
What this PR does:
Introduces a Guide on how to setup UTF-8 mode in Cortex
Which issue(s) this PR fixes:
Fixes #7091
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]docs/configuration/v1-guarantees.mdupdated if this PR introduces experimental flags (does not apply)