| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Filter automatically collected URL query parameters according to Data Collection settings across server, client, tracing, breadcrumb, and failed-request integrations. Preserve raw query values when Data Collection is absent and always filter built-in sensitive parameter names in explicit mode. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
Performance metrics 🚀
Baseline results on branch: feat/data-collection-http-response-headersStartup times
App size
Previous results on branch: feat/data-collection-query-paramsStartup times
App size
|
Sorry, something went wrong.
…ata-collection-query-params
Update URL filtering and integration coverage to consume the renamed canonical Data Collection option. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. This PR will not appear in the changelog. 🤖 This preview updates automatically when you update the PR. |
Sorry, something went wrong.
…ata-collection-query-params
…ata-collection-query-params
Do not apply Data Collection policies while converting completed OpenTelemetry URL attributes. Preserve manually supplied values and leave attribute collection controls to OpenTelemetry. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
…ata-collection-query-params
…ata-collection-query-params
There was a problem hiding this comment.
LGTM 👍
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Stack (Data Collection)
📜 Description
Apply the query-parameter Data Collection policy to Sentry-owned automatic HTTP request data, spans, breadcrumbs, and failed-request events.
The policy is used by Servlet, Spring MVC/WebFlux, OkHttp, Ktor, Apollo 2/3/4, OpenFeign, RestTemplate, and WebClient. Explicit Data Collection supports off, deny-list, and allow-list behavior. Built-in sensitive parameter names are always filtered, including when allow-listed. Encoded parameter names are decoded for matching while the original query encoding is retained.
When Data Collection is absent, integrations continue to attach raw query values as before. Completed OpenTelemetry attributes also retain their existing values because the exporter cannot distinguish manually supplied attributes from values added by auto-instrumentation.
💡 Motivation and Context
Query strings collected by Sentry-owned automatic instrumentation need a dedicated privacy control. This wires dataCollection.urlQueryParams into those Java HTTP integration paths while preserving the legacy bridge for applications that have not configured Data Collection.
Refs #5666
💚 How did you test it?
📝 Checklist
🔮 Next steps
Migrate cookie collection and complete the remaining Data Collection configuration and integration work.
#skip-changelog