Skip to content

Define declarative configuration path for sensitive_query_parameters - #3403

Merged
lmolkova merged 4 commits into
open-telemetry:mainfrom
trask:sensitive-query-parameters
Feb 16, 2026
Merged

lmolkova merged 4 commits into
open-telemetry:mainfrom
trask:sensitive-query-parameters

Conversation

@trask

@trask trask commented Feb 5, 2026

Copy link
Copy Markdown
Member

Similar to

This property doesn't have any precedent for naming, so would be worth considering other options besides sensitive_query_parameters.

cc @open-telemetry/configuration-approvers

@trask
trask force-pushed the sensitive-query-parameters branch 2 times, most recently from 1de903d to 89bf0d9 Compare February 5, 2026 18:50
@github-actions github-actions Bot added enhancement New feature or request area:http labels Feb 5, 2026
@trask
trask marked this pull request as ready for review February 5, 2026 18:51
@trask
trask requested review from a team as code owners February 5, 2026 18:51
Comment thread docs/db/elasticsearch.md Outdated
@trask
trask force-pushed the sensitive-query-parameters branch from 140caff to ad92f42 Compare February 11, 2026 04:29
@lmolkova lmolkova moved this from Untriaged to Needs More Approval in Semantic Conventions Triage Feb 13, 2026
@trask trask moved this from Needs More Approval to Ready to be Merged in Semantic Conventions Triage Feb 13, 2026
@lmolkova
lmolkova added this pull request to the merge queue Feb 16, 2026
Merged via the queue into open-telemetry:main with commit 861dccd Feb 16, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants