Add hosts/auto-detection + K8s quick start plus overview

[dedemorton]

Closes https://github.com/elastic/obs-docs-projects/issues/248

Preview links:

• Quickstarts overview: https://elastic-dot-co-docs-production-5la2m5ml6-elastic-dev.vercel.app/current/serverless/observability/quickstarts/overview (1)
• Monitor hosts with Elastic Agent: https://elastic-dot-co-docs-production-5la2m5ml6-elastic-dev.vercel.app/current/serverless/observability/quickstarts/monitor-hosts-with-elastic-agent
• Monitor your infrastructure with Kubernetes: https://elastic-dot-co-docs-production-5la2m5ml6-elastic-dev.vercel.app/current/serverless/observability/quickstarts/k8s-logs-metrics

(1) We'll add over quickstarts to the list in the overview as they become available.

This PR includes:

• Basic navigation and overview for all the quickstarts:

  

• Topic about auto-detecting logs/metrics (host monitoring) (WIP)

TODO before merging (Host monitoring QS):

• Resolve inline TODO items:
  • Add more detail to this section to highlight "the salient points of the specific dashboards or pages." Waiting for info from SMEs.
  • Decide where to crop the Host overview dashboard...it's kind of big to include it its entirety.

TODO after merging:

• Port to stateful

Open questions

• @thomheymann Akhilesh mentioned that some integrations that are part of this auto-detection based flow are only available for Linux. Which ones? See answer is this comment.
• @thomheymann What advice do we want to give users if they look at the dashboards and realize they've missed some logs they want to ingest. Is there a way to re-run the auto-detection script and add new logs without having uninstall Elastic Agent and go through all the steps again? See answer in this comment.
  IMO, telling users to modify the yaml config would be throwing folks into the deep end.
• @akhileshpok @mykolaharmash Still waiting for your response here.
• @akhileshpok @thomheymann Still waiting for your resonse here.

[mergify]

This pull request does not have a backport label. Could you fix it @dedemorton? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-/d./d is the label to automatically backport to the /d./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[elasticdocs]

🚀 Built elastic-dot-co-docs-preview-docs successfully!

• https://elastic-dot-co-docs-production-5la2m5ml6-elastic-dev.vercel.app

• Built with commit 7ba4e41

Issues? Visit #next-docs in Slack

[akhileshpok]

@dedemorton - Thanks. The draft looks good. A couple of points to consider; a) I believe that under 'Visualize your data' we will only show the call-to-action button once the script has verified that the relevant data has started flowing into ES. Maybe, it is worth mentioning or re-formulating the description accordingly. b) Under the 'Get value out of your data' section, can we briefly describe the salient points of the specific dashboards or pages that we ask the user to explore for each of the supported integrations? This a key part of the quick start flow design, as we will typically select one dashboard or feature per installed integration type. c) Should we consider a dedicated section for 'Constraints or limitations' because there will be a few for each of the new quick start flows? It might be easier to draw the attention of the user if we provide a dedicated section for this content.

[alaudazzi]

@dedemorton

I pushed a first draft of the k8s quickstart, with relevant images.

@mykolaharmash @akhileshpok
How do we want to expand the section Get value out of your data? The dashboards are pretty intuitive with the data you can monitor, but maybe you want to emphasize something in particular?

CC @flash1293

[dedemorton]

@akhileshpok

a) I believe that under 'Visualize your data' we will only show the call-to-action button once the script has verified that the relevant data has started flowing into ES. Maybe, it is worth mentioning or re-formulating the description accordingly.

👍 will do

b) Under the 'Get value out of your data' section, can we briefly describe the salient points of the specific dashboards or pages that we ask the user to explore for each of the supported integrations? This a key part of the quick start flow design, as we will typically select one dashboard or feature per installed integration type.

Great idea! Is there a document somewhere that explains the salient points we want to add about each of the dashboards? I can probably look at the dashboards and summarize each of them, but without more guidance, I'm not sure I can add much value beyond what users can figure out by looking for themselves. If there's no existing document, maybe you or another SME can walk me through the points we want to highlight? Let me know what you think.

c) Should we consider a dedicated section for 'Constraints or limitations' because there will be a few for each of the new quick start flows? It might be easier to draw the attention of the user if we provide a dedicated section for this content.

👍 sure it can be a dedicated section

[dedemorton]

@akhileshpok Check out the lastest preview (linked at the top) and let me know if I'm on the right track. I may need to tweak the headings a little more, but I think we should put the details about available assets under "Visualize your data" so the section maps to what users see in the UI. Let me know what you think.

cc @alaudazzi You might want to wait for feedback before applying parallel changes to your topic.

[alaudazzi]

@dedemorton Thank you for fixing it, and sorry again 🙏

[alaudazzi]

@akhileshpok @mykolaharmash
Here is a doc preview of the K8s quickstart. Would you mind checking if it's OK and if additional content is required?

[dedemorton]

@akhileshpok @thomheymann I am still waiting for feedback/input to finalize this PR (specifically I need to know what we want to say about the integration assets promoted in the quickstart). See the table under "Visualize your data" in the preview. I've filled out one row as an example, but I can put whatever you feel is right.

[akhileshpok]

doc preview of the K8s quickstart

@alaudazzi - Can we please include this image of the flow entry point under step 3 of 'Collect your data'?

Under Visualise your data, '.. the Visualize your data section provides a link to the Kubernetes Cluster Overview dashboard that can be used to monitor the health of the cluster. Further, there are links available to other useful prebuilt dashboards for Kubernetes monitoring.

[akhileshpok]

@dedemorton - In the Quickstarts overview page, probably better to state that 'Auto-detection of logs and metrics for Hosts monitoring'. Auto-detection is not available for other use cases currently.
I will come back to you on the missing descriptions under the Visualize your data section for the Hosts quickstart flow.

[alaudazzi]

@abhishekbhatia1710
I've added the image of the flow entry point under step 3 of 'Collect your data' and updated the page with the text you suggested.

[abhishekbhatia1710]

I'm not sure if I'm the appropriate reviewer for this PR. Is it possible I was tagged by mistake? Please let me know if otherwise.

[akhileshpok]

@alaudazzi - Sorry, but I still don't see the image of the entry point in Step 3. Also, can you please update the title of this section to something like, 'Monitor your Kubernetes cluster with Elastic Agent'? Further, can you please amend the last sentence in first section to, 'The kubectl command installs the standalone Elastic Agent in your Kubernetes cluster ....'. Thanks

[akhileshpok]

@dedemorton - Here are my suggestions on the the missing descriptions under the Visualize your data section for the Hosts quickstart flow.
Docker - Prebuilt dashboard for monitoring the status and health of Docker containers.
Apache - Prebuilt dashboard for monitoring of the Apache HTTP server health using error and access logs data.
Nginx - Prebuilt dashboard for monitoring of the Nginx server health using error and access logs data.
Custom logs - Logs Explorer for analysing the custom logs.

[dedemorton]

@akhileshpok Thanks! BTW the preview links change every time we push a new commit, so you might have been looking at an old build when you were reading Arianna's doc. I've updated the links in the summary.

[dedemorton]

I've applied the requested changes and updated the links in the description to point to the latest build. I think we are ready for a final review! Thanks!

[alaudazzi]

@dedemorton thank you for handling the doc fixes for the k8s quickstart during my sick leave, really appreciate it.

[alaudazzi]

LGTM

[dedemorton]

I'm going to merge this. If additional changes are required, please open an issue to report the change. Thanks!

[mergify]

This pull request does not have a backport label. Could you fix it @dedemorton? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-/d./d is the label to automatically backport to the /d./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.