Update quickstarts for 8.16

[dedemorton]

Description

Updates the Observability quickstarts for version 8.16.0:

• Applies requested changes.
• Adds a few consistency edits.
• Updates screenshots to match 8.16.

Preview links

Please remember to also review the changed lines shown in the Files changed tab.

Stateful:

• https://observability-docs_bk_4582.docs-preview.app.elstc.co/guide/en/observability/master/quickstart-monitor-hosts-with-elastic-agent.html
• https://observability-docs_bk_4582.docs-preview.app.elstc.co/guide/en/observability/master/monitor-k8s-logs-metrics-with-elastic-agent.html
• https://observability-docs_bk_4582.docs-preview.app.elstc.co/guide/en/observability/master/monitor-k8s-otel-edot.html
• https://observability-docs_bk_4582.docs-preview.app.elstc.co/guide/en/observability/master/collect-data-with-aws-firehose.html

Serverless:

• https://observability-docs_bk_4582.docs-preview.app.elstc.co/guide/en/serverless/current/observability-quickstarts-monitor-hosts-with-elastic-agent.html
• https://observability-docs_bk_4582.docs-preview.app.elstc.co/guide/en/serverless/current/observability-quickstarts-k8s-logs-metrics.html
• https://observability-docs_bk_4582.docs-preview.app.elstc.co/guide/en/serverless/current/collect-data-with-aws-firehose.html

Documentation sets edited in this PR

Check all that apply.

• Stateful (docs/en/observability/*)
• Serverless (docs/en/serverless/*)
• Integrations Developer Guide (docs/en/integrations/*)
• None of the above

Related issue

Closes #4534, #4562, and #4563

Checklist

• Product/Engineering Review
• Writer Review

Follow-up tasks

Select one.

• This PR does not need to be ported to another doc set because:
  • The concepts in this PR only apply to one doc set (serverless or stateful)
  • The PR contains edits to both doc sets (serverless and stateful)
• This PR needs to be ported to another doc set:
  • Port to stateful docs: <link to PR or tracking issue>
  • Port to serverless docs: <link to PR or tracking issue>

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[alaudazzi]

@dedemorton @eedugon
Specifically to the section "Collect your data", I would remove the screenshot as it adds no added value to the short list of steps.
More in general, screenshots generate lots of maintenance, especially when documenting new features, as the UI is supposed to change frequently.

[eedugon]

I like the screenshots for this type of docs, at least to get an overview of what you are going to see when you follow the doc, even if it could get a bit outdated at some point.

But whatever you prefer, I completely understand the negative aspects of using screenshots, and as @alaudazzi says, the Collect data specifically doesn't add much value besides helping the user to determine that they are in the right place.

In anyway I would suggest to double check with PMs before removing the screenshots. If everybody agrees I'm totally ok with removing them too.

If the conversation is around the format of the screenshots of the collect data section then I prefer screenshots that show a good portion of the screen, like the one included in https://www.elastic.co/guide/en/observability/current/monitor-k8s-otel-edot.html#_collect_your_data_3 more than the capture of a very small part of the screen that ends up quite big and zoomed in the doc, like https://www.elastic.co/guide/en/observability/current/collect-data-with-aws-firehose.html#_collect_your_data_4.

In the second case I'd try at least to ensure the image doesn't ends up being too big on the final doc.

[dedemorton]

Thanks for you input. Since we're split in the middle, for the review, I think I will include the screenshot (using the version that provides context) and ask PMs to make a case for keeping it. If the onboarding experience is more stable because most of the quickstarts are GA, then maybe it won't change as much going forward.

[akhileshpok]

The doc covering the quickstart onboarding workflow for Firehose in serverless does not mention that this functionality is currently in Tech Preview.

[dedemorton]

The doc covering the quickstart onboarding workflow for Firehose in serverless does not mention that this functionality is currently in Tech Preview.

Good catch! The preview tag must have gotten removed when we did a general cleanup of preview tags for GA. (In some cases, the tag was doing double duty.)

[mdbirnstiehl]

🦭 👍