From ceaaf5163824d102bf64c04de4ec3de91b14277d Mon Sep 17 00:00:00 2001 From: Cody De Arkland Date: Thu, 27 Mar 2025 23:08:20 -0700 Subject: [PATCH 1/4] Removing propagation endpoint, clarifying text --- .../distributed-tracing/how-to-use/javascript.astro.mdx | 8 +++----- .../how-to-use/javascript.cloudflare.mdx | 8 +++----- .../distributed-tracing/how-to-use/javascript.mdx | 6 ++---- .../distributed-tracing/how-to-use/javascript.nextjs.mdx | 6 ++---- .../distributed-tracing/how-to-use/javascript.node.mdx | 6 ++---- .../distributed-tracing/how-to-use/javascript.nuxt.mdx | 6 ++---- .../distributed-tracing/how-to-use/javascript.remix.mdx | 6 ++---- .../how-to-use/javascript.solidstart.mdx | 6 ++---- .../how-to-use/javascript.sveltekit.mdx | 6 ++---- 9 files changed, 20 insertions(+), 38 deletions(-) diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx index 09d81ff38ae00c..83835b6d82ec65 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx @@ -26,19 +26,17 @@ Sentry.init({ tracesSampleRate: 1.0, tracePropagationTargets: [ "https://api.myecommerce.com", - "https://auth.myecommerce.com", - /^\/internal-api\// + "https://auth.myecommerce.com" ], }); ``` -This tells Sentry to track user journeys across three places: +This tells Sentry to pass trace headers across the following paths: * Your main API server (where product data comes from) * Your authentication server (where logins happen) -* Any API calls that start with "/internal-api/" on your current domain -This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services. +This way, if a customer experiences an error during checkout, or you want to check the performance of a specific endpoint, you can see the complete path their request took across these different services. #### Example 2: Mobile App with Backend Services diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.cloudflare.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.cloudflare.mdx index 7688ad53e0f190..4a9c7a96cdbe3e 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.cloudflare.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.cloudflare.mdx @@ -29,19 +29,17 @@ Sentry.init({ tracesSampleRate: 1.0, tracePropagationTargets: [ "https://api.myecommerce.com", - "https://auth.myecommerce.com", - /^\/internal-api\// + "https://auth.myecommerce.com" ], }); ``` -This tells Sentry to track user journeys across three places: +This tells Sentry to pass trace headers across the following paths: * Your main API server (where product data comes from) * Your authentication server (where logins happen) -* Any API calls that start with "/internal-api/" on your current domain -This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services. +This way, if a customer experiences an error during checkout, or you want to check the performance of a specific endpoint, you can see the complete path their request took across these different services. #### Example 2: Mobile App with Backend Services diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.mdx index e295015ca993da..23f4d2e6689ee0 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.mdx @@ -46,18 +46,16 @@ Sentry.init({ tracePropagationTargets: [ "https://api.myecommerce.com", "https://auth.myecommerce.com", - /^\/internal-api\// ], }); ``` -This tells Sentry to track user journeys across three places: +This tells Sentry to pass trace headers across the following paths: * Your main API server (where product data comes from) * Your authentication server (where logins happen) -* Any API calls that start with "/internal-api/" on your current domain -This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services. +This way, if a customer experiences an error during checkout, or you want to check the performance of a specific endpoint, you can see the complete path their request took across these different services. #### Example 2: Mobile App with Backend Services diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx index 5cfc5362d33456..70b942b4b2af50 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx @@ -25,18 +25,16 @@ Sentry.init({ tracePropagationTargets: [ "https://api.myecommerce.com", "https://auth.myecommerce.com", - /^\/internal-api\// ], }); ``` -This tells Sentry to track user journeys across three places: +This tells Sentry to pass trace headers across the following paths: * Your main API server (where product data comes from) * Your authentication server (where logins happen) -* Any API calls that start with "/internal-api/" on your current domain -This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services. +This way, if a customer experiences an error during checkout, or you want to check the performance of a specific endpoint, you can see the complete path their request took across these different services. #### Example 2: Mobile App with Backend Services diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx index 2c00dffbf78bed..5bf558ff2d1aa1 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx @@ -20,18 +20,16 @@ Sentry.init({ tracePropagationTargets: [ "https://api.myecommerce.com", "https://auth.myecommerce.com", - /^\/internal-api\// ], }); ``` -This tells Sentry to track user journeys across three places: +This tells Sentry to pass trace headers across the following paths: * Your main API server (where product data comes from) * Your authentication server (where logins happen) -* Any API calls that start with "/internal-api/" on your current domain -This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services. +This way, if a customer experiences an error during checkout, or you want to check the performance of a specific endpoint, you can see the complete path their request took across these different services. #### Example 2: Mobile App with Backend Services diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx index f9c359e2de9200..f60512074c8652 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx @@ -21,18 +21,16 @@ Sentry.init({ tracePropagationTargets: [ "https://api.myecommerce.com", "https://auth.myecommerce.com", - /^\/internal-api\// ], }); ``` -This tells Sentry to track user journeys across three places: +This tells Sentry to pass trace headers across the following paths: * Your main API server (where product data comes from) * Your authentication server (where logins happen) -* Any API calls that start with "/internal-api/" on your current domain -This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services. +This way, if a customer experiences an error during checkout, or you want to check the performance of a specific endpoint, you can see the complete path their request took across these different services. #### Example 2: Mobile App with Backend Services diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx index 446ceae36ee0d3..7ccebb1dc2ea2b 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx @@ -58,18 +58,16 @@ Sentry.init({ tracePropagationTargets: [ "https://api.myecommerce.com", "https://auth.myecommerce.com", - /^\/internal-api\// ], }); ``` -This tells Sentry to track user journeys across three places: +This tells Sentry to pass trace headers across the following paths: * Your main API server (where product data comes from) * Your authentication server (where logins happen) -* Any API calls that start with "/internal-api/" on your current domain -This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services. +This way, if a customer experiences an error during checkout, or you want to check the performance of a specific endpoint, you can see the complete path their request took across these different services. #### Example 2: Mobile App with Backend Services diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx index 629b78fd8a284c..aa1ee46020f969 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx @@ -52,18 +52,16 @@ Sentry.init({ tracePropagationTargets: [ "https://api.myecommerce.com", "https://auth.myecommerce.com", - /^\/internal-api\// ], }); ``` -This tells Sentry to track user journeys across three places: +This tells Sentry to pass trace headers across the following paths: * Your main API server (where product data comes from) * Your authentication server (where logins happen) -* Any API calls that start with "/internal-api/" on your current domain -This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services. +This way, if a customer experiences an error during checkout, or you want to check the performance of a specific endpoint, you can see the complete path their request took across these different services. #### Example 2: Mobile App with Backend Services diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx index 89f7186e25f181..70ad27d5ae531a 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx @@ -29,18 +29,16 @@ Sentry.init({ tracePropagationTargets: [ "https://api.myecommerce.com", "https://auth.myecommerce.com", - /^\/internal-api\// ], }); ``` -This tells Sentry to track user journeys across three places: +This tells Sentry to pass trace headers across the following paths: * Your main API server (where product data comes from) * Your authentication server (where logins happen) -* Any API calls that start with "/internal-api/" on your current domain -This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services. +This way, if a customer experiences an error during checkout, or you want to check the performance of a specific endpoint, you can see the complete path their request took across these different services. #### Example 2: Mobile App with Backend Services From 5a00274c880fdbd8a61ea587bd63025e65f9a88b Mon Sep 17 00:00:00 2001 From: Cody De Arkland Date: Thu, 27 Mar 2025 23:28:48 -0700 Subject: [PATCH 2/4] Adding trace propagation callout for localhost --- .../how-to-use/javascript.astro.mdx | 8 ++++++++ .../how-to-use/javascript.cloudflare.mdx | 2 +- .../distributed-tracing/how-to-use/javascript.mdx | 8 ++++++++ .../how-to-use/javascript.nextjs.mdx | 8 ++++++++ .../distributed-tracing/how-to-use/javascript.node.mdx | 10 +++++++++- .../distributed-tracing/how-to-use/javascript.nuxt.mdx | 8 ++++++++ .../how-to-use/javascript.remix.mdx | 8 ++++++++ .../how-to-use/javascript.solidstart.mdx | 8 ++++++++ .../how-to-use/javascript.sveltekit.mdx | 8 ++++++++ 9 files changed, 66 insertions(+), 2 deletions(-) diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx index 83835b6d82ec65..14a85afd7790b5 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx @@ -2,6 +2,14 @@ If you're using our Astro SDK, distributed tracing will work out of the box for When you are interacting with other external API systems, you might have to define `tracePropagationTargets` to get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) issues. + + +When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. + +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. + + + ```javascript // sentry.client.config.js Sentry.init({ diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.cloudflare.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.cloudflare.mdx index 4a9c7a96cdbe3e..0c73cfe57e7549 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.cloudflare.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.cloudflare.mdx @@ -2,7 +2,7 @@ The Sentry Cloudflare SDK has out of the box support for distributed tracing if ### Custom Instrumentation -If you don't want to use tracing, you can set up Custom Instrumentation for distributed tracing. +If you don't want to use the default tracing setup, you can set up Custom Instrumentation for distributed tracing. ### Disabling Distributed Tracing diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.mdx index 23f4d2e6689ee0..57662b6303b04d 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.mdx @@ -2,6 +2,14 @@ If you're using the current version of our JavaScript SDK and have enabled the ` To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) issues, define your `tracePropagationTargets`. + + +When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. + +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. + + + ```javascript Sentry.init({ dsn: "___PUBLIC_DSN___", diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx index 70b942b4b2af50..030d8ce2db6f7a 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx @@ -2,6 +2,14 @@ If you're using the current version of our Next.js SDK, distributed tracing will For client-side, when you are interacting with other external API systems, you might have to define `tracePropagationTargets` to get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) issues. + + +When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. + +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. + + + ```javascript // sentry.client.config.js Sentry.init({ diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx index 5bf558ff2d1aa1..c92592bc4f9bd3 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx @@ -8,9 +8,17 @@ Sentry.init({ }); ``` + + +When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. + +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. + + + ### Custom Instrumentation -If you don't want to use tracing, you can set up Custom Instrumentation for distributed tracing. +If you don't want to use the default tracing setup, you can set up Custom Instrumentation for distributed tracing. #### Example 1: Microservices E-commerce Platform diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx index f60512074c8652..320e8d8c3e2d86 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx @@ -2,6 +2,14 @@ If you're using the current version of our Nuxt SDK, distributed tracing will wo To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) issues, you should define `tracePropagationTargets` for client-side. + + +When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. + +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. + + + ```javascript {filename:sentry.client.config.(js|ts)} Sentry.init({ dsn: "___PUBLIC_DSN___", diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx index 7ccebb1dc2ea2b..ce822e830e2ff7 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx @@ -33,6 +33,14 @@ The `name` attributes must be the strings `"sentry-trace"` and `"baggage"` and t To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) issues, you should define `tracePropagationTargets` on the client side. See Dealing with CORS Issues for more information. + + +When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. + +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. + + + ```javascript // entry.client.tsx Sentry.init({ diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx index aa1ee46020f969..def0f91a0289b4 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx @@ -27,6 +27,14 @@ export default defineConfig({ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) issues, you should define `tracePropagationTargets` for client-side. + + +When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. + +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. + + + ```javascript // hooks.client.js Sentry.init({ diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx index 70ad27d5ae531a..64137b55b3f16f 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx @@ -2,6 +2,14 @@ If you're using the current version of our SvelteKit SDK, distributed tracing wi When you are interacting with other external API systems, you might have to define `tracePropagationTargets` to get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) issues. + + +When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. + +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. + + + ```javascript // hooks.client.js Sentry.init({ From cebdcfa5cab20b9c022162c5e5352378a348d4f7 Mon Sep 17 00:00:00 2001 From: Cody De Arkland Date: Thu, 27 Mar 2025 23:34:53 -0700 Subject: [PATCH 3/4] Correcting language for trace prop example --- .../distributed-tracing/how-to-use/javascript.astro.mdx | 4 ++-- .../distributed-tracing/how-to-use/javascript.mdx | 4 ++-- .../distributed-tracing/how-to-use/javascript.nextjs.mdx | 4 ++-- .../distributed-tracing/how-to-use/javascript.node.mdx | 4 ++-- .../distributed-tracing/how-to-use/javascript.nuxt.mdx | 4 ++-- .../distributed-tracing/how-to-use/javascript.remix.mdx | 4 ++-- .../distributed-tracing/how-to-use/javascript.solidstart.mdx | 4 ++-- .../distributed-tracing/how-to-use/javascript.sveltekit.mdx | 4 ++-- 8 files changed, 16 insertions(+), 16 deletions(-) diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx index 14a85afd7790b5..9eb0d7fbc07fb8 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx @@ -4,9 +4,9 @@ When you are interacting with other external API systems, you might have to defi -When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. +Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.mdx index 57662b6303b04d..ec5c1e92f73ff8 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.mdx @@ -4,9 +4,9 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W -When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. +Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx index 030d8ce2db6f7a..08619bdd9410c1 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx @@ -4,9 +4,9 @@ For client-side, when you are interacting with other external API systems, you m -When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. +Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx index c92592bc4f9bd3..808c15059635a0 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx @@ -10,9 +10,9 @@ Sentry.init({ -When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. +Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx index 320e8d8c3e2d86..7021b3cf8edd92 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx @@ -4,9 +4,9 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W -When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. +Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx index ce822e830e2ff7..5551c9d1b16408 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx @@ -35,9 +35,9 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W -When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. +Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx index def0f91a0289b4..504c242af54e03 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx @@ -29,9 +29,9 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W -When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. +Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx index 64137b55b3f16f..1d41ac66bc3241 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx @@ -4,9 +4,9 @@ When you are interacting with other external API systems, you might have to defi -When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. +Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array. +For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. From 5cc6ae255fc093c436357f779872514d39fa08d5 Mon Sep 17 00:00:00 2001 From: Cody De Arkland Date: Sun, 30 Mar 2025 21:50:42 -0700 Subject: [PATCH 4/4] Updating clarification on the tracePropagation configuration. --- .../distributed-tracing/how-to-use/javascript.astro.mdx | 2 +- platform-includes/distributed-tracing/how-to-use/javascript.mdx | 2 +- .../distributed-tracing/how-to-use/javascript.nextjs.mdx | 2 +- .../distributed-tracing/how-to-use/javascript.node.mdx | 2 +- .../distributed-tracing/how-to-use/javascript.nuxt.mdx | 2 +- .../distributed-tracing/how-to-use/javascript.remix.mdx | 2 +- .../distributed-tracing/how-to-use/javascript.solidstart.mdx | 2 +- .../distributed-tracing/how-to-use/javascript.sveltekit.mdx | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx index 9eb0d7fbc07fb8..e4f7c86b47fb03 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx @@ -6,7 +6,7 @@ When you are interacting with other external API systems, you might have to defi Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. +For example, if you have a Node.js backend running locally on port 3000, that destination (`http://localhost:3000`) should be added to the `tracePropagationTargets` array on your frontend to ensure that CORS doesn't restrict the propagation of traces. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.mdx index ec5c1e92f73ff8..6b50a7924fc846 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.mdx @@ -6,7 +6,7 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. +For example, if you have a Node.js backend running locally on port 3000, that destination (`http://localhost:3000`) should be added to the `tracePropagationTargets` array on your frontend to ensure that CORS doesn't restrict the propagation of traces. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx index 08619bdd9410c1..3a12a629dfbf3e 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx @@ -6,7 +6,7 @@ For client-side, when you are interacting with other external API systems, you m Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. +For example, if you have a Node.js backend running locally on port 3000, that destination (`http://localhost:3000`) should be added to the `tracePropagationTargets` array on your frontend to ensure that CORS doesn't restrict the propagation of traces. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx index 808c15059635a0..8e27e136e525cd 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.node.mdx @@ -12,7 +12,7 @@ Sentry.init({ Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. +For example, if you have a Node.js backend running locally on port 3000, that destination (`http://localhost:3000`) should be added to the `tracePropagationTargets` array on your frontend to ensure that CORS doesn't restrict the propagation of traces. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx index 7021b3cf8edd92..c0756a680c563c 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx @@ -6,7 +6,7 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. +For example, if you have a Node.js backend running locally on port 3000, that destination (`http://localhost:3000`) should be added to the `tracePropagationTargets` array on your frontend to ensure that CORS doesn't restrict the propagation of traces. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx index 5551c9d1b16408..ffd06215d2f28c 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx @@ -37,7 +37,7 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. +For example, if you have a Node.js backend running locally on port 3000, that destination (`http://localhost:3000`) should be added to the `tracePropagationTargets` array on your frontend to ensure that CORS doesn't restrict the propagation of traces. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx index 504c242af54e03..c9a28f16de064b 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx @@ -31,7 +31,7 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. +For example, if you have a Node.js backend running locally on port 3000, that destination (`http://localhost:3000`) should be added to the `tracePropagationTargets` array on your frontend to ensure that CORS doesn't restrict the propagation of traces. diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx index 1d41ac66bc3241..81a50bd9f535b1 100644 --- a/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx +++ b/platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx @@ -6,7 +6,7 @@ When you are interacting with other external API systems, you might have to defi Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. -For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array. +For example, if you have a Node.js backend running locally on port 3000, that destination (`http://localhost:3000`) should be added to the `tracePropagationTargets` array on your frontend to ensure that CORS doesn't restrict the propagation of traces.