From e3036adafdc8a4804c400b8abe7faed303384c86 Mon Sep 17 00:00:00 2001 From: Alex Krawiec Date: Fri, 1 Nov 2024 13:40:52 -0700 Subject: [PATCH 1/2] Add links to tracing product page in tracing tutorial --- .../distributed-tracing/initialize-sentry-sdk-backend.mdx | 6 ++---- .../distributed-tracing/initialize-sentry-sdk-frontend.mdx | 4 ++-- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-backend.mdx b/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-backend.mdx index 9a877baa0676d..25b2a41d8438b 100644 --- a/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-backend.mdx +++ b/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-backend.mdx @@ -31,8 +31,6 @@ Sentry captures data by using a platform-specific SDK that you add to your appli 1. Navigate to the `tracing-tutorial-backend` project folder and install the Sentry Express SDK using NPM. - {/* TODO: UPDATE NAME OF THIS REPO */} - ```bash {tabTitle:npm} npm install --save @sentry/node @sentry/profiling-node ``` @@ -80,8 +78,8 @@ Sentry captures data by using a platform-specific SDK that you add to your appli The options set in `Sentry.init()` are called the SDK's configuration. The only required configuration option is the DSN. However, the SDK supports many other configuration options. Learn more in our [Configuration](/platforms/javascript/guides/react/configuration/) docs. - The configuration above enables Sentry's error monitoring feature, as well as its **Tracing** and [Session Replay](/platforms/javascript/guides/react/session-replay) features. - {/* TODO: Add link for tracing here when tracing doc is live */} + The configuration above enables Sentry's error monitoring feature, as well as its [**Tracing**](/product/tracing/) and [**Session Replay**](/platforms/javascript/guides/react/session-replay) features. + 1. Import `instrument.js` at the top of your `server.js` file. Then import `Sentry` and set up the error handler after all controllers and before any other middleware: diff --git a/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx b/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx index f2868396c85fa..8d76b7afc9a32 100644 --- a/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx +++ b/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx @@ -85,8 +85,8 @@ Sentry captures data by using a platform-specific SDK that you add to your appli The options set in `Sentry.init()` are called the SDK's configuration. The only required configuration option is the DSN. However, the SDK supports many other configuration options. Learn more in our [Configuration](/platforms/javascript/guides/react/configuration/) docs. -The configuration above enables Sentry's error monitoring feature, as well as **tracing** and [Session Replay](/platforms/javascript/guides/react/session-replay) features. Take note of the `tracePropagationTargets` option, this is required to enable tracing on any urls your projects are running on. Since both of this tutorial's projects are running on `localhost`, we are all set. -{/* TODO: Add link for tracing here when tracing doc is live */} +The configuration above enables Sentry's error monitoring feature, as well as [**tracing**](/product/tracing/) and [**Session Replay**](/platforms/javascript/guides/react/session-replay) features. Take note of the `tracePropagationTargets` option, this is required to enable tracing on any urls your projects are running on. Since both of this tutorial's projects are running on `localhost`, we are all set. + ## 3. Build and Run the Sample Application From 946dbbbb15db7e7d38fbbbfec25168a5d9a03c2d Mon Sep 17 00:00:00 2001 From: Alex Krawiec Date: Fri, 1 Nov 2024 13:42:41 -0700 Subject: [PATCH 2/2] Fix capitalization typo --- .../distributed-tracing/initialize-sentry-sdk-frontend.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx b/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx index 8d76b7afc9a32..8bb3a4517745a 100644 --- a/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx +++ b/docs/product/sentry-basics/distributed-tracing/initialize-sentry-sdk-frontend.mdx @@ -85,7 +85,7 @@ Sentry captures data by using a platform-specific SDK that you add to your appli The options set in `Sentry.init()` are called the SDK's configuration. The only required configuration option is the DSN. However, the SDK supports many other configuration options. Learn more in our [Configuration](/platforms/javascript/guides/react/configuration/) docs. -The configuration above enables Sentry's error monitoring feature, as well as [**tracing**](/product/tracing/) and [**Session Replay**](/platforms/javascript/guides/react/session-replay) features. Take note of the `tracePropagationTargets` option, this is required to enable tracing on any urls your projects are running on. Since both of this tutorial's projects are running on `localhost`, we are all set. +The configuration above enables Sentry's error monitoring feature, as well as [**Tracing**](/product/tracing/) and [**Session Replay**](/platforms/javascript/guides/react/session-replay) features. Take note of the `tracePropagationTargets` option, this is required to enable tracing on any urls your projects are running on. Since both of this tutorial's projects are running on `localhost`, we are all set. ## 3. Build and Run the Sample Application