diff --git a/docs/platforms/php/common/crons/troubleshooting.mdx b/docs/platforms/php/common/crons/troubleshooting.mdx
deleted file mode 100644
index 7ca3cac8c66e1..0000000000000
--- a/docs/platforms/php/common/crons/troubleshooting.mdx
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Troubleshooting
-description: "Learn how to troubleshoot your Cron Monitoring setup."
-sidebar_order: 9000
----
-
-
-
-
-
-You may not have linked errors to your monitor.
-
-
-
-
-
-You may not have set up alerts for your monitor.
-
-
-
-
-
-Our current data retention policy is 90 days.
-
-
-
-
-
-Currently, we only support crontab expressions with five fields.
-
-
-
-
-
-You can either consider running your jobs in the background OR use the `checkInMargin` option to make the window larger.
-
-
diff --git a/docs/platforms/php/common/profiling/troubleshooting.mdx b/docs/platforms/php/common/profiling/troubleshooting.mdx
deleted file mode 100644
index f0f4db734701f..0000000000000
--- a/docs/platforms/php/common/profiling/troubleshooting.mdx
+++ /dev/null
@@ -1,12 +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 Tracing is enabled.
-- Ensure that the custom instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io).
-- Ensure the `Sentry\Integration\EnvironmentIntegration` is enabled.
-- Enable the logger to see what the SDK is doing under the hood.
diff --git a/docs/platforms/php/common/tracing/troubleshooting/index.mdx b/docs/platforms/php/common/tracing/troubleshooting/index.mdx
deleted file mode 100644
index 91680e839de3e..0000000000000
--- a/docs/platforms/php/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`
-
-
diff --git a/docs/platforms/php/common/troubleshooting/index.mdx b/docs/platforms/php/common/troubleshooting/index.mdx
index 4c50c083ecb20..27058d800d404 100644
--- a/docs/platforms/php/common/troubleshooting/index.mdx
+++ b/docs/platforms/php/common/troubleshooting/index.mdx
@@ -4,7 +4,9 @@ sidebar_order: 9000
description: "Troubleshooting steps for PHP"
---
-## Log SDK internal events
+## General
+
+
A good first step to debug SDK issues is using the `logger` option. For your convenience, the SDK ships with two implementations, `DebugFileLogger` and `DebugStdOutLogger`.
@@ -31,7 +33,76 @@ sentry/sentry: [warning] The profile does not contain enough samples, the profil
sentry/sentry: [info] Sent transaction [59390dc9dd934c0290d8cdc7a589da82] to o1.ingest.sentry.io [project:1]. Result: "success" (status: 200).
```
+
-## Missing Variables in Stack Traces
+
This is caused by the PHP configuration. PHP 7.4 introduced a new .ini setting, `zend.exception_ignore_args`, that will ignore stack trace arguments. Check your .ini file to ensure this setting is set to `Off` or `0`.
+
+
+
+
+
+ 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`
+
+
+
+
+
+
+## Profiling
+
+
+
+If you don't see any profiling data in [sentry.io](https://sentry.io), you can try the following:
+
+ - Ensure that Tracing is enabled.
+ - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io).
+ - Ensure that the custom instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io).
+ - Ensure the `Sentry\Integration\EnvironmentIntegration` is enabled.
+ - Enable the logger to see what the SDK is doing under the hood.
+
+
+
+## Crons
+
+
+
+
+
+
+ You may not have linked errors to your monitor.
+
+
+
+
+
+ You may not have set up alerts for your monitor.
+
+
+
+
+
+ Our current data retention policy is 90 days.
+
+
+
+
+
+ Currently, we only support crontab expressions with five fields.
+
+
+
+
+
+ You can either consider running your jobs in the background OR use the `checkInMargin` option to make the window larger.
+
+
diff --git a/docs/platforms/php/guides/laravel/profiling/troubleshooting.mdx b/docs/platforms/php/guides/laravel/profiling/troubleshooting.mdx
deleted file mode 100644
index b776f35942f03..0000000000000
--- a/docs/platforms/php/guides/laravel/profiling/troubleshooting.mdx
+++ /dev/null
@@ -1,12 +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 Tracing is enabled.
-- 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 custom instrumentation.
-- Ensure the `Sentry\Integration\EnvironmentIntegration` is enabled.
diff --git a/docs/platforms/php/guides/symfony/profiling/troubleshooting.mdx b/docs/platforms/php/guides/symfony/profiling/troubleshooting.mdx
deleted file mode 100644
index b776f35942f03..0000000000000
--- a/docs/platforms/php/guides/symfony/profiling/troubleshooting.mdx
+++ /dev/null
@@ -1,12 +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 Tracing is enabled.
-- 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 custom instrumentation.
-- Ensure the `Sentry\Integration\EnvironmentIntegration` is enabled.
diff --git a/redirects.js b/redirects.js
index 5ce5c460f4765..3b46445448b9c 100644
--- a/redirects.js
+++ b/redirects.js
@@ -972,6 +972,14 @@ const userDocsRedirects = [
source: '/platforms/ruby/:productfeature/troubleshooting/:path*',
destination: '/platforms/ruby/troubleshooting/:path*',
},
+ {
+ source: '/platforms/php/guides/:guide/:productfeature/troubleshooting/:path*',
+ destination: '/platforms/php/guides/:guide/troubleshooting/:path*',
+ },
+ {
+ source: '/platforms/php/:productfeature/troubleshooting/:path*',
+ destination: '/platforms/php/troubleshooting/:path*',
+ },
];
/**