diff --git a/docs/platforms/android/data-management/sensitive-data/index.mdx b/docs/platforms/android/data-management/sensitive-data/index.mdx index 1e7e1640163bca..341b30cc930d6c 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 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/apple/common/data-management/sensitive-data/index.mdx b/docs/platforms/apple/common/data-management/sensitive-data/index.mdx index 7ae640f698c818..db724767f31ec6 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 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/dart/data-management/sensitive-data/index.mdx b/docs/platforms/dart/data-management/sensitive-data/index.mdx index 7ae640f698c818..db724767f31ec6 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 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 1e7e1640163bca..341b30cc930d6c 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 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 7ae640f698c818..db724767f31ec6 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 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 7ae640f698c818..db724767f31ec6 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 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 7ae640f698c818..db724767f31ec6 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 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 1e7e1640163bca..341b30cc930d6c 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 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 5099fbc97671e1..ddce8cc2536971 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 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 1e7e1640163bca..341b30cc930d6c 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 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 1e7e1640163bca..341b30cc930d6c 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 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 ecd908ba7ae522..db70735ac85278 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 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 7ae640f698c818..db724767f31ec6 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 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 222354aa935ffe..085e5c912cbc6e 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 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 1e7e1640163bca..341b30cc930d6c 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 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/platform-includes/sensitive-data/scrubbing-data/native.mdx b/platform-includes/sensitive-data/scrubbing-data/native.mdx index 968e4a34e34154..bf14564b179871 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 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.