helm: Log access-policy and token names in GEM query-frontend #9348
+37
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does
r308 allows GEM gateway to enable passing the access-policy-name and token-name to mimir backends with the request headers. This enables GEM customers to get a better insight in who is running a query, by logging these headers in the query-frontend query stats. This PR enables updates the Helm chart, enabling this by default.
Below is an example for it looks in the query-frontend logs:
That is, in addition to the
user=tenant-1
that query-frontend logs already, we now log the following:header_x_access_policy_name=test-access-policy-1
— the access policy nameheader_x_token_name=test-access-policy-1-token-1
— the full token nameChecklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.