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

[Serverless] Document impact of using logsDB for security users #6221

Merged
merged 15 commits into from
Dec 2, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/serverless/rules/detections-logsdb-impact.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ LogsDB is enabled by default for Elastic serverless. This topic explains the imp

With logsDB index mode, the original `_source` field is not stored in the index but can be reconstructed using {ref}/mapping-source-field.html#synthetic-source[synthetic `_source`].

When the `_source` is reconstructed, you can make {ref}/mapping-source-field.html#synthetic-source-modifications[modifications] close to the original data. However, there could be a mismatch between how users expect field values to be formatted.
When the `_source` is reconstructed, {ref}/mapping-source-field.html#synthetic-source-modifications[modifications] are possible. Therefore, there could be a mismatch between how users expect field values to be formatted.
nastasha-solomon marked this conversation as resolved.
Show resolved Hide resolved

nastasha-solomon marked this conversation as resolved.
Show resolved Hide resolved
Continue reading to find out how this affects specific {sec-serverless} components.

Expand Down