Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.16](backport #4384) Add docs for new central log source setting #4401

Merged
merged 2 commits into from
Oct 18, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 18, 2024

Description

Document the new Kibana log source advanced setting that provides a centralized place to store log index patterns that other solutions can access instead of hardcoding index patterns in different places.

This PR updates all of the places in the o11y docs where we were documenting using hardcoded log index patterns and replaces them with the logs source setting.

We will need to update the Kibana advanced settings in another PR. The Discover docs may need an update as well.

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 #4316

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>

This is an automatic backport of pull request #4384 done by [Mergify](https://mergify.com).

* update docs for new centra log source setting

* update ML page

(cherry picked from commit 0fb7cdd)

# Conflicts:
#	docs/en/serverless/logging/view-and-monitor-logs.mdx
@mergify mergify bot requested a review from a team as a code owner October 18, 2024 20:50
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Oct 18, 2024
Copy link
Contributor Author

mergify bot commented Oct 18, 2024

Cherry-pick of 0fb7cdd has failed:

On branch mergify/bp/8.16/pr-4384
Your branch is up to date with 'origin/8.16'.

You are currently cherry-picking commit 0fb7cdd0.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   docs/en/observability/categorize-logs.asciidoc
	modified:   docs/en/observability/configure-logs-sources.asciidoc
	modified:   docs/en/observability/explore-logs.asciidoc
	modified:   docs/en/observability/inspect-log-anomalies.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/en/serverless/logging/view-and-monitor-logs.mdx

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link
Contributor

A documentation preview will be available soon.

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.

@bmorelli25 bmorelli25 enabled auto-merge (squash) October 18, 2024 20:52
@bmorelli25 bmorelli25 merged commit 4416b29 into 8.16 Oct 18, 2024
3 checks passed
@bmorelli25 bmorelli25 deleted the mergify/bp/8.16/pr-4384 branch October 18, 2024 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants