Adding trace propagation callout for localhost

Author: codyde

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.
 
+<Alert>
+
+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.
+
+</Alert>
+
 ```javascript
 // sentry.client.config.js
 Sentry.init({

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 <PlatformLink to="/tracing/trace-propagation/custom-instrumentation/">Custom Instrumentation</PlatformLink> for distributed tracing.
+If you don't want to use the default tracing setup, you can set up <PlatformLink to="/tracing/trace-propagation/custom-instrumentation/">Custom Instrumentation</PlatformLink> for distributed tracing.
 
 ### Disabling Distributed Tracing
 

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`.
 
+<Alert>
+
+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.
+
+</Alert>
+
 ```javascript
 Sentry.init({
   dsn: "___PUBLIC_DSN___",

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.
 
+<Alert>
+
+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.
+
+</Alert>
+
 ```javascript
 // sentry.client.config.js
 Sentry.init({

platform-includes/distributed-tracing/how-to-use/javascript.node.mdx

@@ -8,9 +8,17 @@ Sentry.init({
 });
 ```
 
+<Alert>
+
+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.
+
+</Alert>
+
 ### Custom Instrumentation
 
-If you don't want to use tracing, you can set up <PlatformLink to="/tracing/trace-propagation/custom-instrumentation/">Custom Instrumentation</PlatformLink> for distributed tracing.
+If you don't want to use the default tracing setup, you can set up <PlatformLink to="/tracing/trace-propagation/custom-instrumentation/">Custom Instrumentation</PlatformLink> for distributed tracing.
 
 #### Example 1: Microservices E-commerce Platform
 

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.
 
+<Alert>
+
+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.
+
+</Alert>
+
 ```javascript {filename:sentry.client.config.(js|ts)}
 Sentry.init({
   dsn: "___PUBLIC_DSN___",

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 <PlatformLink to="/tracing/trace-propagation/dealing-with-cors-issues/">Dealing with CORS Issues</PlatformLink> for more information.
 
+<Alert>
+
+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.
+
+</Alert>
+
 ```javascript
 // entry.client.tsx
 Sentry.init({

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.
 
+<Alert>
+
+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.
+
+</Alert>
+
 ```javascript
 // hooks.client.js
 Sentry.init({

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.
 
+<Alert>
+
+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.
+
+</Alert>
+
 ```javascript
 // hooks.client.js
 Sentry.init({