Create log data set monitoring docs

[mdbirnstiehl]

Closes #3344

Because the system is set to accept all logs, users need to be able to monitor their data sets to find and fix any issues that occur in their log data. The information found on this page will serve as a foundation for the user to monitor the overall health of their data sets and find any data sets with issues and fix them. The data set quality page will available through Stack Management.

[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 @mdbirnstiehl? 🙏
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.

[mdbirnstiehl]

@gbamparop I've update the data set monitoring docs here to provide some general information and tips on investigating issues. Is there any additional guidance you think we should provide users at this point?

@awahab07 I added the privilege requirements here

[alaudazzi]

Left a minor editing suggestion.

[mergify]

This pull request is now in conflict. Could you fix it @mdbirnstiehl? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b monitor-datasets upstream/monitor-datasets
git merge upstream/main
git push upstream monitor-datasets

[yngrdyn]

Hey @mdbirnstiehl thanks for creating this PR, I was not able to check the preview, it has like an old version (without the changes) is that expected?

[gbamparop]

@mdbirnstiehl will the stateful docs be added in another PR?

[mdbirnstiehl]

@mdbirnstiehl will the stateful docs be added in another PR?

@gbamparop I was waiting until we finalized the serverless docs and then I was planning on basing the stateful docs off of them. I can either add them to this PR after the serverless docs are finalized or create a new PR.

One question is whether or not there will be significant changes between the two that would require any large rewrites.

[yngrdyn]

One question is whether or not there will be significant changes between the two that would require any large rewrites.

Changes so far are not substancial, only around size column and summary, Size is not available on serverless at the moment, only stateful

[elasticdocs]

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

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

• Built with commit 785ef98

Issues? Visit #next-docs in Slack

[mdbirnstiehl]

Hey @mdbirnstiehl thanks for creating this PR, I was not able to check the preview, it has like an old version (without the changes) is that expected?

@yngrdyn sorry I missed this initially. You can view the preview for serverless here . I had forgotten to add the doc build label.

[yngrdyn]

LGTM, the only thing is that screenshot is outdated.
It's showing logs-* instead of logs-*-*

[alaudazzi]

LGTM