port changes from stateful docs

docs/en/serverless/apm/apm-troubleshooting/common-problems.asciidoc

@@ -3,33 +3,7 @@
 This section describes common problems you might encounter.
 
 ////
-/* * <DocLink slug="/serverless/observability/apm-troubleshooting" section="no-data-is-indexed">No data is indexed</DocLink>
-* <DocLink slug="/serverless/observability/apm-troubleshooting">APM Server response codes</DocLink>
-* <DocLink slug="/serverless/observability/apm-troubleshooting" section="common-ssl-related-problems">Common SSL-related problems</DocLink>
-* <DocLink slug="/serverless/observability/apm-troubleshooting" section="io-timeout">I/O Timeout</DocLink>
-* <DocLink slug="/serverless/observability/apm-troubleshooting" section="field-limit-exceeded">Field limit exceeded</DocLink> */
-////
-
-[discrete]
-[[no-data-is-indexed]]
-=== No data is indexed
-
-If no data shows up, first make sure that your APM components are properly connected.
-
-include::../../transclusion/apm/guide/tab-widgets/no-data-indexed/fleet-managed.asciidoc[]
-
-[discrete]
-[[data-indexed-no-apm-legacy]]
-=== Data is indexed but doesn't appear in the Applications UI
-
-Elastic APM relies on default index mappings, data streams, and pipelines to query and display data.
-If your APM data isn't showing up in the Applications UI, but is elsewhere in Elastic, like Discover,
-you've likely made a change that overwrote a default.
-If you've manually changed a data stream, index template, or index pipeline,
-please verify you are not interfering with the default APM setup.
-
-////
-/* ### I/O Timeout
+### I/O Timeout
 
 I/O Timeouts can occur when your timeout settings across the stack are not configured correctly,
 especially when using a load balancer.