Restructure Node performance instrumentation pages.

Author: onurtemizkan

src/platform-includes/performance/connect-services/node.mdx

@@ -0,0 +1,5 @@
+If you are also using Performance Monitoring for [JavaScript](/platforms/javascript/performance/), depending on where your request originates, you can connect traces:
+1. For requests that start in your backend, by [adding a meta tag](/platforms/javascript/performance/connect-services/#pageload) in your HTML template that contains tracing information.
+2. For requests that start in JavaScript, by the SDK [setting a header](/platforms/javascript/performance/connect-services/#navigation-and-other-xhr-requests) on requests to your backend.
+
+Otherwise, backend services with Performance Monitoring connect automatically.

src/platforms/common/performance/connect-services.mdx

@@ -12,7 +12,7 @@ SDKs with performance monitoring support listen to incoming requests and typical
 
 If the instrumentation you are using doesn't automatically pick up the `sentry-trace` header, you can also continue a trace manually by using the `continueFromHeaders` function on a `Transaction`, which you can learn more about in our content for [the Transaction Interface](https://develop.sentry.dev/sdk/performance/#new-span-and-transaction-classes).
 
-<PlatformSection supported={["android", "javascript"]} notSupported={["node"]}>
+<PlatformSection supported={["android", "javascript", "node"]}>
 
 <PlatformContent includePath="performance/connect-services" />
 

src/platforms/common/performance/index.mdx

@@ -90,7 +90,7 @@ Learn more about how the options work in <PlatformLink to="/configuration/sampli
 
 ## Verify
 
-<PlatformSection supported={["react-native", "java.spring", "java.spring-boot", "android", "javascript", "apple", "dart", "rust"]} notSupported={["node"]} >
+<PlatformSection supported={["react-native", "java.spring", "java.spring-boot", "android", "javascript", "apple", "dart", "rust"]}>
 
 Verify that performance monitoring is working correctly by using our <PlatformLink to="/performance/instrumentation/automatic-instrumentation/">automatic instrumentation</PlatformLink> or by starting and finishing a transaction using <PlatformLink to="/performance/instrumentation/custom-instrumentation/">custom instrumentation</PlatformLink>.
 

src/platforms/common/performance/instrumentation/custom-instrumentation.mdx

@@ -4,6 +4,7 @@ sidebar_order: 20
 supported:
   - javascript
   - javascript.cordova
+  - node
   - react-native
   - dotnet
   - python

src/platforms/common/performance/instrumentation/index.mdx

@@ -4,7 +4,6 @@ sidebar_order: 20
 description: "Learn how to instrument performance in your app."
 notSupported:
   - javascript.cordova
-  - node
   - native.breakpad
   - native.crashpad
   - native.minidumps

src/platforms/node/common/performance/instrumentation/index.mdx renamed to src/platforms/node/common/performance/instrumentation/automatic-instrumentation.mdx

@@ -1,6 +1,11 @@
 ---
-title: Instrumentation
-description: "Learn more about how to configure our Performance integrations to get the best experience out of it."
+title: Automatic Instrumentation
+sidebar_order: 10
+supported:
+  - node
+description: "Learn what transactions are captured after tracing is enabled."
+redirect_from:
+  - /performance/included-instrumentation
 ---
 
 By default, Sentry error events will not get trace context unless you configure the scope with the transaction, as illustrated in the example below.
@@ -62,27 +67,6 @@ request.on("close", () => {
 });
 ```
 
-## Custom Instrumentation
-
-To instrument a specific region of your code, you can create a transaction to capture it.
-
-The following example creates a transaction for a part of the code that contains an expensive operation (for example, `processItem`), and sends the result to Sentry:
-
-```javascript
-app.use(function processItems(req, res, next) {
-  const item = getFromQueue();
-  const transaction = Sentry.startTransaction({
-    op: "task",
-    name: item.getTransaction(),
-  });
-
-  // processItem may create more spans internally (see next examples)
-  processItem(item, transaction).then(() => {
-    transaction.finish();
-    next();
-  });
-});
-```
 
 ### Retrieving a Transaction
 
@@ -105,11 +89,3 @@ app.get("/success", function successHandler(req, res) {
   res.status(200).end();
 });
 ```
-
-## Connecting Services
-
-If you are also using Performance Monitoring for [JavaScript](/platforms/javascript/performance/), depending on where your request originates, you can connect traces:
-1. For requests that start in your backend, by [adding a meta tag](/platforms/javascript/performance/connect-services/#pageload) in your HTML template that contains tracing information.
-2. For requests that start in JavaScript, by the SDK [setting a header](/platforms/javascript/performance/connect-services/#navigation-and-other-xhr-requests) on requests to your backend.
-
-Otherwise, backend services with Performance Monitoring connect automatically.