First take on a comprehensive ingest guide

[karenzone]

New take on ingest story.

• Start by trying to answer the question we hear most: "What ingest option should I use?"
• Start with basic use cases and expand to more advanced use cases.
• Proposal: Get to MVP quickly, and continue to iterate.

PREVIEW: https://ingest-docs_bk_1373.docs-preview.app.elstc.co/guide/en/ingest/master/ingest-guide.html

Notes

• I've placed the content at the end of Ingest Architectures temporarily so that we can build it and see previews. This is not intended as the final destination.

Related:

• https://github.com/elastic/platform-docs-team/issues/489
• https://github.com/elastic/platform-docs-team/issues/545

[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.}

[mergify]

This pull request does not have a backport label. Could you fix it @karenzone? 🙏
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.

[karenzone]

Ordinarily, we wouldn't put forth a list of tools. Because we have quite a few ingest options and we highlight subsets throughout our doc sets, it seems helpful to list all ingest tools with descriptions in one place.

[karenzone]

MVP proposal

This PR includes the elements that we decided were "must have" for an MVP:

• Answer the most commonly asked question about ingesting data--"What's the best approach?"
  • Focus on starting basic, but making it clear up front that we can handle more complex scenarios if needed
• Describe ingest options and when they should be used
• Emphasize solutions, encouraging users to start with Agent and integrations.

Next iteration

Issue to capture feedback and ideas for next iteration: https://github.com/elastic/platform-docs-team/issues/545

[karenzone]

@kilfoyle @alaudazzi @mdbirnstiehl @georgewallace, thank you for your comments in the previous markup.io review.
Now that we're in the refinement stage, please add your feedback as github suggestions and comments.
And as always, please let me know if you'd like to discuss.