Skip to content

Commit ceaaf51

Browse files
committed
Removing propagation endpoint, clarifying text
1 parent f219234 commit ceaaf51

File tree

9 files changed

+20
-38
lines changed

9 files changed

+20
-38
lines changed

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

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,19 +26,17 @@ Sentry.init({
2626
tracesSampleRate: 1.0,
2727
tracePropagationTargets: [
2828
"https://api.myecommerce.com",
29-
"https://auth.myecommerce.com",
30-
/^\/internal-api\//
29+
"https://auth.myecommerce.com"
3130
],
3231
});
3332
```
3433

35-
This tells Sentry to track user journeys across three places:
34+
This tells Sentry to pass trace headers across the following paths:
3635

3736
* Your main API server (where product data comes from)
3837
* Your authentication server (where logins happen)
39-
* Any API calls that start with "/internal-api/" on your current domain
4038

41-
This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services.
39+
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.
4240

4341
#### Example 2: Mobile App with Backend Services
4442

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

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -29,19 +29,17 @@ Sentry.init({
2929
tracesSampleRate: 1.0,
3030
tracePropagationTargets: [
3131
"https://api.myecommerce.com",
32-
"https://auth.myecommerce.com",
33-
/^\/internal-api\//
32+
"https://auth.myecommerce.com"
3433
],
3534
});
3635
```
3736

38-
This tells Sentry to track user journeys across three places:
37+
This tells Sentry to pass trace headers across the following paths:
3938

4039
* Your main API server (where product data comes from)
4140
* Your authentication server (where logins happen)
42-
* Any API calls that start with "/internal-api/" on your current domain
4341

44-
This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services.
42+
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.
4543

4644
#### Example 2: Mobile App with Backend Services
4745

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -46,18 +46,16 @@ Sentry.init({
4646
tracePropagationTargets: [
4747
"https://api.myecommerce.com",
4848
"https://auth.myecommerce.com",
49-
/^\/internal-api\//
5049
],
5150
});
5251
```
5352

54-
This tells Sentry to track user journeys across three places:
53+
This tells Sentry to pass trace headers across the following paths:
5554

5655
* Your main API server (where product data comes from)
5756
* Your authentication server (where logins happen)
58-
* Any API calls that start with "/internal-api/" on your current domain
5957

60-
This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services.
58+
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.
6159

6260
#### Example 2: Mobile App with Backend Services
6361

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,18 +25,16 @@ Sentry.init({
2525
tracePropagationTargets: [
2626
"https://api.myecommerce.com",
2727
"https://auth.myecommerce.com",
28-
/^\/internal-api\//
2928
],
3029
});
3130
```
3231

33-
This tells Sentry to track user journeys across three places:
32+
This tells Sentry to pass trace headers across the following paths:
3433

3534
* Your main API server (where product data comes from)
3635
* Your authentication server (where logins happen)
37-
* Any API calls that start with "/internal-api/" on your current domain
3836

39-
This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services.
37+
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.
4038

4139
#### Example 2: Mobile App with Backend Services
4240

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,18 +20,16 @@ Sentry.init({
2020
tracePropagationTargets: [
2121
"https://api.myecommerce.com",
2222
"https://auth.myecommerce.com",
23-
/^\/internal-api\//
2423
],
2524
});
2625
```
2726

28-
This tells Sentry to track user journeys across three places:
27+
This tells Sentry to pass trace headers across the following paths:
2928

3029
* Your main API server (where product data comes from)
3130
* Your authentication server (where logins happen)
32-
* Any API calls that start with "/internal-api/" on your current domain
3331

34-
This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services.
32+
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.
3533

3634
#### Example 2: Mobile App with Backend Services
3735

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,18 +21,16 @@ Sentry.init({
2121
tracePropagationTargets: [
2222
"https://api.myecommerce.com",
2323
"https://auth.myecommerce.com",
24-
/^\/internal-api\//
2524
],
2625
});
2726
```
2827

29-
This tells Sentry to track user journeys across three places:
28+
This tells Sentry to pass trace headers across the following paths:
3029

3130
* Your main API server (where product data comes from)
3231
* Your authentication server (where logins happen)
33-
* Any API calls that start with "/internal-api/" on your current domain
3432

35-
This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services.
33+
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.
3634

3735
#### Example 2: Mobile App with Backend Services
3836

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,18 +58,16 @@ Sentry.init({
5858
tracePropagationTargets: [
5959
"https://api.myecommerce.com",
6060
"https://auth.myecommerce.com",
61-
/^\/internal-api\//
6261
],
6362
});
6463
```
6564

66-
This tells Sentry to track user journeys across three places:
65+
This tells Sentry to pass trace headers across the following paths:
6766

6867
* Your main API server (where product data comes from)
6968
* Your authentication server (where logins happen)
70-
* Any API calls that start with "/internal-api/" on your current domain
7169

72-
This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services.
70+
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.
7371

7472
#### Example 2: Mobile App with Backend Services
7573

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -52,18 +52,16 @@ Sentry.init({
5252
tracePropagationTargets: [
5353
"https://api.myecommerce.com",
5454
"https://auth.myecommerce.com",
55-
/^\/internal-api\//
5655
],
5756
});
5857
```
5958

60-
This tells Sentry to track user journeys across three places:
59+
This tells Sentry to pass trace headers across the following paths:
6160

6261
* Your main API server (where product data comes from)
6362
* Your authentication server (where logins happen)
64-
* Any API calls that start with "/internal-api/" on your current domain
6563

66-
This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services.
64+
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.
6765

6866
#### Example 2: Mobile App with Backend Services
6967

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,18 +29,16 @@ Sentry.init({
2929
tracePropagationTargets: [
3030
"https://api.myecommerce.com",
3131
"https://auth.myecommerce.com",
32-
/^\/internal-api\//
3332
],
3433
});
3534
```
3635

37-
This tells Sentry to track user journeys across three places:
36+
This tells Sentry to pass trace headers across the following paths:
3837

3938
* Your main API server (where product data comes from)
4039
* Your authentication server (where logins happen)
41-
* Any API calls that start with "/internal-api/" on your current domain
4240

43-
This way, if a customer experiences an error during checkout, you can see the complete path their request took across these different services.
41+
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.
4442

4543
#### Example 2: Mobile App with Backend Services
4644

0 commit comments

Comments
 (0)