You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
filebeat/filestream: default include_file_fingerprint to true (#51793) (#51839)
Soft-revert of #50129, which made log.file.fingerprint in published
events opt-in via include_file_fingerprint (default false). Removing the
field by default is technically a breaking change that we don't
understand fully yet.
Users who want to save network, indexing, and storage costs at scale can
set include_file_fingerprint to false. A still-growing fingerprint is
never published.
After further benchmarks we can re-consider if we want to make the
breaking change and flip the default to false.
Reclassify the changelog fragment from breaking-change to enhancement.
(cherry picked from commit 8e39946)
Co-authored-by: Orestis Floros <orestis.floros@elastic.co>
Copy file name to clipboardExpand all lines: docs/reference/filebeat/filebeat-input-filestream.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -723,7 +723,7 @@ This option is not supported on Windows.
723
723
```yaml {applies_to}
724
724
stack: ga 9.5.0
725
725
```
726
-
Controls whether `log.file.fingerprint` is added to published events. Only takes effect when `file_identity.fingerprint` is configured. Defaults to `false`. The file path (`log.file.path`) is always present in events regardless of this setting.
726
+
Controls whether `log.file.fingerprint` is added to published events. Only takes effect when `file_identity.fingerprint` is configured. Defaults to `true`. The file path (`log.file.path`) is always present in events regardless of this setting.
0 commit comments