Skip to content

[8.17] [8.17-8.18] More changes to the LogsDB page (backport #6639) #6785

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

Merged
merged 1 commit into from
Apr 21, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 21, 2025

Description

Contributes to #6526, which requests changes to the note about logsdb and additional information to help users who have enabled logsdb index mode or are considering it. The corresponding 9.0 and Serverless docs are at: elastic/docs-content#878

Preview

Using logsdb index mode with Elastic Security: Made the following changes:

  • Modified the second sentence in the note as per the request in the doc issue. Now it says: Logsdb index mode is fully supported, and is recommended for all Elastic Security deployments. Users with existing Elastic Security deployments are advised to fully understand and accept the documented changes...
  • Added a new section that briefly explains how logsdb index mode might affect CPU and storage usage and links users to an Elastic blog post with recent benchmarks.
  • Expanded the "Runtime fields" section by adding guidance for handling runtime fields with scripts that reference the params._source field.

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

* First draft

* Redundant

* Update detections-logsdb-impact.asciidoc

* change tense

* Small fixes

* One more change

(cherry picked from commit 4c4cc44)
@mergify mergify bot requested a review from a team as a code owner April 21, 2025 21:44
@mergify mergify bot added the backport label Apr 21, 2025
Copy link

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.

@nastasha-solomon nastasha-solomon enabled auto-merge (squash) April 21, 2025 21:48
@nastasha-solomon nastasha-solomon merged commit d260416 into 8.17 Apr 21, 2025
5 checks passed
@nastasha-solomon nastasha-solomon deleted the mergify/bp/8.17/pr-6639 branch April 21, 2025 22:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant