diff --git a/docs/platforms/ruby/common/crons/troubleshooting.mdx b/docs/platforms/ruby/common/crons/troubleshooting.mdx
deleted file mode 100644
index 9d92124e718c59..00000000000000
--- a/docs/platforms/ruby/common/crons/troubleshooting.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Troubleshooting
-description: "Learn how to troubleshoot your Cron Monitoring setup."
-sidebar_order: 9000
----
-
-<PlatformContent includePath="crons/troubleshooting" />
-
-<Expandable title="Why aren't recurring job errors showing up on my monitor details page?">
-
-You may not have <PlatformLink to="/crons/#connecting-errors-to-cron-monitors">linked errors to your monitor</PlatformLink>.
-
-</Expandable>
-
-<Expandable title="Why am I not receiving alerts when my monitor fails?">
-
-You may not have <PlatformLink to="/crons/#alerts">set up alerts for your monitor</PlatformLink>.
-
-</Expandable>
-
-<Expandable title="What is the crons data retention policy for check-ins?">
-
-Our current data retention policy is 90 days.
-
-</Expandable>
-
-<Expandable title="Do you support a monitor schedule with a six-field crontab expression?">
-
-Currently, we only support crontab expressions with five fields.
-
-</Expandable>
diff --git a/docs/platforms/ruby/common/profiling/troubleshooting/index.mdx b/docs/platforms/ruby/common/profiling/troubleshooting/index.mdx
deleted file mode 100644
index 0cfd2acac02f9d..00000000000000
--- a/docs/platforms/ruby/common/profiling/troubleshooting/index.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Troubleshooting
-description: "Learn how to troubleshoot your profiling setup."
-sidebar_order: 9000
----
-
-If you don't see any profiling data in [sentry.io](https://sentry.io), you can try the following:
-
-- Ensure that <PlatformLink to="/tracing/">Tracing is enabled</PlatformLink>.
-- Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io).
-- If the automatic instrumentation is not sending performance data, try using <PlatformLink to="/tracing/instrumentation/custom-instrumentation">custom instrumentation</PlatformLink>.
-- Enable <PlatformLink to="/configuration/options/#debug">debug mode</PlatformLink> in the SDK and check the logs.
-
-### Limitations
-
-Profiles for multi-threaded servers like `puma` might not capture frames correctly when async I/O is happening. This is a limitation of `stackprof`.
diff --git a/docs/platforms/ruby/common/tracing/troubleshooting/index.mdx b/docs/platforms/ruby/common/tracing/troubleshooting/index.mdx
deleted file mode 100644
index 91680e839de3e8..00000000000000
--- a/docs/platforms/ruby/common/tracing/troubleshooting/index.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Troubleshooting
-description: "Learn how to troubleshoot your tracing setup."
-sidebar_order: 9000
----
-
-If you need help managing transactions, you can read more here. If you need additional help, you can ask on GitHub. Customers on a paid plan may also contact support.
-
-## Control Data Truncation
-
-Currently, every tag has a maximum character limit of 200 characters. Tags over the 200 character limit will become truncated, losing potentially important information. To retain this data, you can split data over several tags instead.
-
-For example, a 200+ character tagged request:
-
-`https://empowerplant.io/api/0/projects/ep/setup_form/?user_id=314159265358979323846264338327&tracking_id=EasyAsABC123OrSimpleAsDoReMi&product_name=PlantToHumanTranslator&product_id=161803398874989484820458683436563811772030917980576`
-
-The 200+ character request above will become truncated to:
-
-`https://empowerplant.io/api/0/projects/ep/setup_form/?user_id=314159265358979323846264338327&tracking_id=EasyAsABC123OrSimpleAsDoReMi&product_name=PlantToHumanTranslator&product_id=1618033988749894848`
-
-<PlatformContent includePath="performance/control-data-truncation" />
diff --git a/docs/platforms/ruby/common/troubleshooting.mdx b/docs/platforms/ruby/common/troubleshooting.mdx
new file mode 100644
index 00000000000000..39b0a86c7cff8b
--- /dev/null
+++ b/docs/platforms/ruby/common/troubleshooting.mdx
@@ -0,0 +1,68 @@
+---
+title: Troubleshooting
+description: "Learn how to troubleshoot your SDK setup."
+sidebar_order: 9000
+---
+
+## General
+
+<Expandable title="Why was my tag value truncated?">
+
+  Currently, every tag has a maximum character limit of 200 characters. Tags over the 200 character limit will become truncated, losing potentially important information. To retain this data, you can split data over several tags instead.
+
+  For example, a 200+ character tagged request:
+
+  `https://empowerplant.io/api/0/projects/ep/setup_form/?user_id=314159265358979323846264338327&tracking_id=EasyAsABC123OrSimpleAsDoReMi&product_name=PlantToHumanTranslator&product_id=161803398874989484820458683436563811772030917980576`
+
+  The 200+ character request above will become truncated to:
+
+  `https://empowerplant.io/api/0/projects/ep/setup_form/?user_id=314159265358979323846264338327&tracking_id=EasyAsABC123OrSimpleAsDoReMi&product_name=PlantToHumanTranslator&product_id=1618033988749894848`
+
+</Expandable>
+
+## Profiling
+
+<Expandable title="Why am I not seeing any profiling data?">
+
+  If you don't see any profiling data in [sentry.io](https://sentry.io), you can try the following:
+
+  - Ensure that <PlatformLink to="/tracing/">Tracing is enabled</PlatformLink>.
+  - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page
+  in [sentry.io](https://sentry.io).
+  - If the automatic instrumentation is not sending performance data, try using <PlatformLink
+  to="/tracing/instrumentation/custom-instrumentation">custom instrumentation</PlatformLink>.
+  - Enable <PlatformLink to="/configuration/options/#debug">debug mode</PlatformLink> in the SDK and check the logs.
+
+  ### Limitations
+
+  Profiles for multi-threaded servers like `puma` might not capture frames correctly when async I/O is happening. This
+  is a limitation of `stackprof`.
+</Expandable>
+
+## Crons
+
+<PlatformContent includePath="crons/troubleshooting" />
+
+<Expandable title="Why aren't recurring job errors showing up on my monitor details page?">
+
+You may not have <PlatformLink to="/crons/#connecting-errors-to-cron-monitors">linked errors to your monitor</PlatformLink>.
+
+</Expandable>
+
+<Expandable title="Why am I not receiving alerts when my monitor fails?">
+
+You may not have <PlatformLink to="/crons/#alerts">set up alerts for your monitor</PlatformLink>.
+
+</Expandable>
+
+<Expandable title="What is the crons data retention policy for check-ins?">
+
+Our current data retention policy is 90 days.
+
+</Expandable>
+
+<Expandable title="Do you support a monitor schedule with a six-field crontab expression?">
+
+Currently, we only support crontab expressions with five fields.
+
+</Expandable>
diff --git a/redirects.js b/redirects.js
index bd13262490f69c..5ce5c460f47652 100644
--- a/redirects.js
+++ b/redirects.js
@@ -964,6 +964,14 @@ const userDocsRedirects = [
     source: '/product/explore/feature-flags/:path*',
     destination: '/product/issues/issue-details/feature-flags/:path*',
   },
+  {
+    source: '/platforms/ruby/guides/:guide/:productfeature/troubleshooting/:path*',
+    destination: '/platforms/ruby/guides/:guide/troubleshooting/:path*',
+  },
+  {
+    source: '/platforms/ruby/:productfeature/troubleshooting/:path*',
+    destination: '/platforms/ruby/troubleshooting/:path*',
+  },
 ];
 
 /**