[8.17-8.18] More changes to the LogsDB page #6639
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nastasha-solomon
added
Team: Detection Engine
Priority: High
|
A documentation preview will be available soon. Request a new doc build by commenting
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. |
…ty-docs into issue-6526-logsdb-updates
|
Hi, I see that the preview docs linked in this PR say "To learn more about how logsdb index mode optimizes CPU and storage usage..." but the blog that it links to doesn't talk about CPU optimization. |
| [[logsdb-cpu-storage]] | ||
| == CPU and storage | ||
|
|
||
| Logsdb index mode significantly reduces storage needs by using slightly more CPU during ingest. After enabling logsdb index mode for your data sources, you may need to adjust cluster sizing in response to the new CPU and storage needs. To learn more about how logsdb index mode optimizes CPU and storage usage, check out https://www.elastic.co/search-labs/blog/elasticsearch-logsdb-index-mode[our blog]. |
There was a problem hiding this comment.
Hey, @tylerperk thanks for the feedback. Would you prefer that the docs link to a different blog? Or are you instead recommending that the last sentence be revised, for example:
Suggested change
| Logsdb index mode significantly reduces storage needs by using slightly more CPU during ingest. After enabling logsdb index mode for your data sources, you may need to adjust cluster sizing in response to the new CPU and storage needs. To learn more about how logsdb index mode optimizes CPU and storage usage, check out https://www.elastic.co/search-labs/blog/elasticsearch-logsdb-index-mode[our blog]. | |
| Logsdb index mode significantly reduces storage needs by using slightly more CPU during ingest. After enabling logsdb index mode for your data sources, you may need to adjust cluster sizing in response to the new CPU and storage needs. To learn more about how logsdb index mode optimizes storage usage, check out https://www.elastic.co/search-labs/blog/elasticsearch-logsdb-index-mode[our blog]. |
mergify bot
pushed a commit
that referenced
this pull request
Apr 21, 2025
* First draft * Redundant * Update detections-logsdb-impact.asciidoc * change tense * Small fixes * One more change (cherry picked from commit 4c4cc44)
mergify bot
pushed a commit
that referenced
this pull request
Apr 21, 2025
* First draft * Redundant * Update detections-logsdb-impact.asciidoc * change tense * Small fixes * One more change (cherry picked from commit 4c4cc44)
nastasha-solomon
added a commit
to elastic/docs-content
that referenced
this pull request
Apr 21, 2025
### Description Contributes to elastic/security-docs#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 8.18 docs are at: elastic/security-docs#6639 ### Preview [Using logsdb index mode with Elastic Security](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/878/solutions/security/detect-and-alert/using-logsdb-index-mode-with-elastic-security)
nastasha-solomon
added a commit
that referenced
this pull request
Apr 21, 2025
* First draft * Redundant * Update detections-logsdb-impact.asciidoc * change tense * Small fixes * One more change (cherry picked from commit 4c4cc44) Co-authored-by: Nastasha Solomon <[email protected]>
nastasha-solomon
added a commit
that referenced
this pull request
Apr 21, 2025
* First draft * Redundant * Update detections-logsdb-impact.asciidoc * change tense * Small fixes * One more change (cherry picked from commit 4c4cc44) Co-authored-by: Nastasha Solomon <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
params._sourcefield.