Skip to content

Conversation

@charleskorn
Copy link
Contributor

For example, requests that return NOT_FOUND or FAILED_PRECONDITION would be grouped together and show an empty series name.

…ts with an underscore in their status code
@charleskorn charleskorn merged commit 5627ad0 into master Oct 27, 2025
10 checks passed
@charleskorn charleskorn deleted the charleskorn/allow-underscores branch October 27, 2025 23:32
charleskorn added a commit to grafana/mimir that referenced this pull request Oct 28, 2025
#### What this PR does

This PR brings in the fix from
grafana/jsonnet-libs#1519.

#### Which issue(s) this PR fixes or relates to

(none)

#### Checklist

- [n/a] Tests updated.
- [n/a] Documentation added.
- [x] `CHANGELOG.md` updated - the order of entries should be
`[CHANGE]`, `[FEATURE]`, `[ENHANCEMENT]`, `[BUGFIX]`. If changelog entry
is not needed, please add the `changelog-not-needed` label to the PR.
- [n/a]
[`about-versioning.md`](https://github.com/grafana/mimir/blob/main/docs/sources/mimir/configure/about-versioning.md)
updated with experimental features.
@bboreham
Copy link
Contributor

Why do we restrict any status codes there?

Eg suppose someone puts CLOUD9, that will get transformed to "" the same way as the underscores.

@charleskorn
Copy link
Contributor Author

Why do we restrict any status codes there?

Eg suppose someone puts CLOUD9, that will get transformed to "" the same way as the underscores.

The main purpose of the regex is to differentiate between the HTTP case (numeric status code) and gRPC status code (string like OK or CANCELED).

We could extend the pattern to support other strings as well, but the gRPC status codes as they currently stand only include A-Z and underscores.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants