From 1f71c3b007ba08e6a23bb9b66e9cde697840b5df Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Tue, 3 Dec 2024 14:31:28 +0100 Subject: [PATCH 1/5] feat: Scrubbing HTTP Data from HTTP Spans Explain that most SDKs will add the HTTP query string and fragment as a data attribute to spans. --- docs/platforms/android/data-management/sensitive-data/index.mdx | 1 + .../apple/common/data-management/sensitive-data/index.mdx | 1 + docs/platforms/dart/data-management/sensitive-data/index.mdx | 1 + .../dotnet/common/data-management/sensitive-data/index.mdx | 1 + docs/platforms/elixir/data-management/sensitive-data/index.mdx | 1 + docs/platforms/flutter/data-management/sensitive-data/index.mdx | 1 + .../platforms/go/common/data-management/sensitive-data/index.mdx | 1 + .../java/common/data-management/sensitive-data/index.mdx | 1 + .../javascript/common/data-management/sensitive-data/index.mdx | 1 + .../php/common/data-management/sensitive-data/index.mdx | 1 + .../powershell/data-management/sensitive-data/index.mdx | 1 + docs/platforms/python/data-management/sensitive-data/index.mdx | 1 + .../react-native/data-management/sensitive-data/index.mdx | 1 + .../ruby/common/data-management/sensitive-data/index.mdx | 1 + .../rust/common/data-management/sensitive-data/index.mdx | 1 + platform-includes/sensitive-data/scrubbing-data/native.mdx | 1 + 16 files changed, 16 insertions(+) diff --git a/docs/platforms/android/data-management/sensitive-data/index.mdx b/docs/platforms/android/data-management/sensitive-data/index.mdx index 1e7e1640163bc..2a47808281046 100644 --- a/docs/platforms/android/data-management/sensitive-data/index.mdx +++ b/docs/platforms/android/data-management/sensitive-data/index.mdx @@ -54,6 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/apple/common/data-management/sensitive-data/index.mdx b/docs/platforms/apple/common/data-management/sensitive-data/index.mdx index 7ae640f698c81..c975a5ecf5745 100644 --- a/docs/platforms/apple/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/apple/common/data-management/sensitive-data/index.mdx @@ -48,6 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/dart/data-management/sensitive-data/index.mdx b/docs/platforms/dart/data-management/sensitive-data/index.mdx index 7ae640f698c81..c975a5ecf5745 100644 --- a/docs/platforms/dart/data-management/sensitive-data/index.mdx +++ b/docs/platforms/dart/data-management/sensitive-data/index.mdx @@ -48,6 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx b/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx index 1e7e1640163bc..2a47808281046 100644 --- a/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx @@ -54,6 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/elixir/data-management/sensitive-data/index.mdx b/docs/platforms/elixir/data-management/sensitive-data/index.mdx index 7ae640f698c81..c975a5ecf5745 100644 --- a/docs/platforms/elixir/data-management/sensitive-data/index.mdx +++ b/docs/platforms/elixir/data-management/sensitive-data/index.mdx @@ -48,6 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/flutter/data-management/sensitive-data/index.mdx b/docs/platforms/flutter/data-management/sensitive-data/index.mdx index 7ae640f698c81..c975a5ecf5745 100644 --- a/docs/platforms/flutter/data-management/sensitive-data/index.mdx +++ b/docs/platforms/flutter/data-management/sensitive-data/index.mdx @@ -48,6 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/go/common/data-management/sensitive-data/index.mdx b/docs/platforms/go/common/data-management/sensitive-data/index.mdx index 7ae640f698c81..c975a5ecf5745 100644 --- a/docs/platforms/go/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/go/common/data-management/sensitive-data/index.mdx @@ -48,6 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/java/common/data-management/sensitive-data/index.mdx b/docs/platforms/java/common/data-management/sensitive-data/index.mdx index 1e7e1640163bc..2a47808281046 100644 --- a/docs/platforms/java/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/java/common/data-management/sensitive-data/index.mdx @@ -54,6 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx b/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx index 5099fbc97671e..e867bced15088 100644 --- a/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx @@ -49,6 +49,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/php/common/data-management/sensitive-data/index.mdx b/docs/platforms/php/common/data-management/sensitive-data/index.mdx index 1e7e1640163bc..2a47808281046 100644 --- a/docs/platforms/php/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/php/common/data-management/sensitive-data/index.mdx @@ -54,6 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/powershell/data-management/sensitive-data/index.mdx b/docs/platforms/powershell/data-management/sensitive-data/index.mdx index 1e7e1640163bc..2a47808281046 100644 --- a/docs/platforms/powershell/data-management/sensitive-data/index.mdx +++ b/docs/platforms/powershell/data-management/sensitive-data/index.mdx @@ -54,6 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/python/data-management/sensitive-data/index.mdx b/docs/platforms/python/data-management/sensitive-data/index.mdx index ecd908ba7ae52..144085fbbb679 100644 --- a/docs/platforms/python/data-management/sensitive-data/index.mdx +++ b/docs/platforms/python/data-management/sensitive-data/index.mdx @@ -60,6 +60,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/react-native/data-management/sensitive-data/index.mdx b/docs/platforms/react-native/data-management/sensitive-data/index.mdx index 7ae640f698c81..c975a5ecf5745 100644 --- a/docs/platforms/react-native/data-management/sensitive-data/index.mdx +++ b/docs/platforms/react-native/data-management/sensitive-data/index.mdx @@ -48,6 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx b/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx index 222354aa935ff..d4675a6d9c9a9 100644 --- a/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx @@ -50,6 +50,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/rust/common/data-management/sensitive-data/index.mdx b/docs/platforms/rust/common/data-management/sensitive-data/index.mdx index 1e7e1640163bc..2a47808281046 100644 --- a/docs/platforms/rust/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/rust/common/data-management/sensitive-data/index.mdx @@ -54,6 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/platform-includes/sensitive-data/scrubbing-data/native.mdx b/platform-includes/sensitive-data/scrubbing-data/native.mdx index 968e4a34e3415..2e08ed32d99b0 100644 --- a/platform-includes/sensitive-data/scrubbing-data/native.mdx +++ b/platform-includes/sensitive-data/scrubbing-data/native.mdx @@ -13,6 +13,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. +- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. From 219402c0ff6eb95af8100cf540d75d6b32376e5a Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Thu, 12 Dec 2024 10:33:37 +0100 Subject: [PATCH 2/5] Update docs/platforms/android/data-management/sensitive-data/index.mdx Co-authored-by: Liza Mock --- docs/platforms/android/data-management/sensitive-data/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/android/data-management/sensitive-data/index.mdx b/docs/platforms/android/data-management/sensitive-data/index.mdx index 2a47808281046..341b30cc930d6 100644 --- a/docs/platforms/android/data-management/sensitive-data/index.mdx +++ b/docs/platforms/android/data-management/sensitive-data/index.mdx @@ -54,7 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. From c69f84ff58f2b4d4853689a09f96ce4769a9cabd Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Thu, 12 Dec 2024 10:33:47 +0100 Subject: [PATCH 3/5] Update platform-includes/sensitive-data/scrubbing-data/native.mdx Co-authored-by: Liza Mock --- platform-includes/sensitive-data/scrubbing-data/native.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platform-includes/sensitive-data/scrubbing-data/native.mdx b/platform-includes/sensitive-data/scrubbing-data/native.mdx index 2e08ed32d99b0..bf14564b17987 100644 --- a/platform-includes/sensitive-data/scrubbing-data/native.mdx +++ b/platform-includes/sensitive-data/scrubbing-data/native.mdx @@ -13,7 +13,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. From fd6961e8257f4e5c0ef58a98e3479ef78b80d110 Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Thu, 12 Dec 2024 10:33:56 +0100 Subject: [PATCH 4/5] Update docs/platforms/apple/common/data-management/sensitive-data/index.mdx Co-authored-by: Liza Mock --- .../apple/common/data-management/sensitive-data/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/apple/common/data-management/sensitive-data/index.mdx b/docs/platforms/apple/common/data-management/sensitive-data/index.mdx index c975a5ecf5745..db724767f31ec 100644 --- a/docs/platforms/apple/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/apple/common/data-management/sensitive-data/index.mdx @@ -48,7 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. From aec35c2e3bfa29922f2e3658541c87e454a5e462 Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Thu, 12 Dec 2024 10:35:40 +0100 Subject: [PATCH 5/5] review --- docs/platforms/dart/data-management/sensitive-data/index.mdx | 2 +- .../dotnet/common/data-management/sensitive-data/index.mdx | 2 +- docs/platforms/elixir/data-management/sensitive-data/index.mdx | 2 +- docs/platforms/flutter/data-management/sensitive-data/index.mdx | 2 +- .../go/common/data-management/sensitive-data/index.mdx | 2 +- .../java/common/data-management/sensitive-data/index.mdx | 2 +- .../javascript/common/data-management/sensitive-data/index.mdx | 2 +- .../php/common/data-management/sensitive-data/index.mdx | 2 +- .../powershell/data-management/sensitive-data/index.mdx | 2 +- docs/platforms/python/data-management/sensitive-data/index.mdx | 2 +- .../react-native/data-management/sensitive-data/index.mdx | 2 +- .../ruby/common/data-management/sensitive-data/index.mdx | 2 +- .../rust/common/data-management/sensitive-data/index.mdx | 2 +- 13 files changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/platforms/dart/data-management/sensitive-data/index.mdx b/docs/platforms/dart/data-management/sensitive-data/index.mdx index c975a5ecf5745..db724767f31ec 100644 --- a/docs/platforms/dart/data-management/sensitive-data/index.mdx +++ b/docs/platforms/dart/data-management/sensitive-data/index.mdx @@ -48,7 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx b/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx index 2a47808281046..341b30cc930d6 100644 --- a/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx @@ -54,7 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/elixir/data-management/sensitive-data/index.mdx b/docs/platforms/elixir/data-management/sensitive-data/index.mdx index c975a5ecf5745..db724767f31ec 100644 --- a/docs/platforms/elixir/data-management/sensitive-data/index.mdx +++ b/docs/platforms/elixir/data-management/sensitive-data/index.mdx @@ -48,7 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/flutter/data-management/sensitive-data/index.mdx b/docs/platforms/flutter/data-management/sensitive-data/index.mdx index c975a5ecf5745..db724767f31ec 100644 --- a/docs/platforms/flutter/data-management/sensitive-data/index.mdx +++ b/docs/platforms/flutter/data-management/sensitive-data/index.mdx @@ -48,7 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/go/common/data-management/sensitive-data/index.mdx b/docs/platforms/go/common/data-management/sensitive-data/index.mdx index c975a5ecf5745..db724767f31ec 100644 --- a/docs/platforms/go/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/go/common/data-management/sensitive-data/index.mdx @@ -48,7 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/java/common/data-management/sensitive-data/index.mdx b/docs/platforms/java/common/data-management/sensitive-data/index.mdx index 2a47808281046..341b30cc930d6 100644 --- a/docs/platforms/java/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/java/common/data-management/sensitive-data/index.mdx @@ -54,7 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx b/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx index e867bced15088..ddce8cc253697 100644 --- a/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx @@ -49,7 +49,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/php/common/data-management/sensitive-data/index.mdx b/docs/platforms/php/common/data-management/sensitive-data/index.mdx index 2a47808281046..341b30cc930d6 100644 --- a/docs/platforms/php/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/php/common/data-management/sensitive-data/index.mdx @@ -54,7 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/powershell/data-management/sensitive-data/index.mdx b/docs/platforms/powershell/data-management/sensitive-data/index.mdx index 2a47808281046..341b30cc930d6 100644 --- a/docs/platforms/powershell/data-management/sensitive-data/index.mdx +++ b/docs/platforms/powershell/data-management/sensitive-data/index.mdx @@ -54,7 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/python/data-management/sensitive-data/index.mdx b/docs/platforms/python/data-management/sensitive-data/index.mdx index 144085fbbb679..db70735ac8527 100644 --- a/docs/platforms/python/data-management/sensitive-data/index.mdx +++ b/docs/platforms/python/data-management/sensitive-data/index.mdx @@ -60,7 +60,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/react-native/data-management/sensitive-data/index.mdx b/docs/platforms/react-native/data-management/sensitive-data/index.mdx index c975a5ecf5745..db724767f31ec 100644 --- a/docs/platforms/react-native/data-management/sensitive-data/index.mdx +++ b/docs/platforms/react-native/data-management/sensitive-data/index.mdx @@ -48,7 +48,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx b/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx index d4675a6d9c9a9..085e5c912cbc6 100644 --- a/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx @@ -50,7 +50,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events. diff --git a/docs/platforms/rust/common/data-management/sensitive-data/index.mdx b/docs/platforms/rust/common/data-management/sensitive-data/index.mdx index 2a47808281046..341b30cc930d6 100644 --- a/docs/platforms/rust/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/rust/common/data-management/sensitive-data/index.mdx @@ -54,7 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events.