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.17-8.18] More changes to the LogsDB page #6639

Open
wants to merge 8 commits into
base: 8.x
Choose a base branch
from

Conversation

nastasha-solomon
Copy link
Contributor

@nastasha-solomon nastasha-solomon commented Mar 18, 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.

@nastasha-solomon nastasha-solomon added Team: Detection Engine Priority: High Issues that are time-sensitive and/or are of high customer importance Effort: Small Issues that can be resolved quickly v8.17.0 v8.18.0 labels Mar 18, 2025
@nastasha-solomon nastasha-solomon self-assigned this Mar 18, 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 marked this pull request as ready for review March 18, 2025 19:30
@nastasha-solomon nastasha-solomon requested a review from a team as a code owner March 18, 2025 19:30
Copy link
Contributor

@marshallmain marshallmain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Effort: Small Issues that can be resolved quickly Priority: High Issues that are time-sensitive and/or are of high customer importance Team: Detection Engine v8.17.0 v8.18.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants