[Serverless]: Troubleshooting page should also include some Serverless specific troubleshooting tips

[KOTungseth]

Serverless Docs

Elastic Observability Serverless

Description

• https://www.elastic.co/current/serverless/observability/troubleshoot-logs
• https://www.elastic.co/docs/current/serverless/observability/apm-troubleshooting
• https://www.elastic.co/current/serverless/observability/troubleshooting-infrastructure-monitoring
• https://www.elastic.co/current/serverless/observability/synthetics-troubleshooting

We may want to rework these sections to include troubleshooting scenarios that are specific to Serverless (or at least include some examples that are not just core Observability troubleshooting).

Original issue: elastic/docs-content#81

[colleenmcginnis]

@KOTungseth @ppf2 are there any Serverless-specific problems that Observability users are currently experiencing? I don't think we've seen any come through in issues or other feedback channels.

[KOTungseth]

I've been unable to find Observability Serverless-specific content we should add to the Docs.

@ppf2 do you know who would have more information?

[ppf2]

For non-Serverless, we have:
https://www.elastic.co/guide/en/observability/current/apm-troubleshoot-apm.html

For Serverless we have:
https://www.elastic.co/guide/en/serverless/current/observability-apm-troubleshooting.html

The Serverless documentation has some duplicate information and is a reduced set. For example, take response codes from APM as an example:

• On Serverless side, we mention 400 and 401 errors.
• On non-Serverless side, we mention 400, 401, 403, 503.

These differences are likely expected because 403 are specific to RUM and RUM is not yet available on Serverless and 503s may no longer be an issue with autoscaling on Serverless ...

Though I think some of the non-Serverless common problems may apply to Serverless as well but it's not captured in Serverless documentation. I can imagine (for example) that things like "Field limit exceeded" and "Fields are not searchable" would still be applicable to Serverless.

cc: @lucabelluccini