Skip to content

Commit 5409d19

Browse files
Fix YAML indentation in parsers examples (#29663) (#29894)
See discussion on https://discuss.elastic.co/t/filebeat-filestream-input-parsers-multiline-fails/290543/9. (cherry picked from commit 9e0dad7) Co-authored-by: Steve Mokris <[email protected]>
1 parent 89fd50e commit 5409d19

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

filebeat/docs/inputs/input-filestream-reader-options.asciidoc

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -164,11 +164,11 @@ The multiline message is stored under the key `msg`.
164164
...
165165
parsers:
166166
- ndjson:
167-
keys_under_root: true
168-
message_key: msg
167+
keys_under_root: true
168+
message_key: msg
169169
- multiline:
170-
type: counter
171-
lines_count: 3
170+
type: counter
171+
lines_count: 3
172172
----
173173

174174
See the available parser settings in detail below.
@@ -197,9 +197,9 @@ Example configuration:
197197
[source,yaml]
198198
----
199199
- ndjson:
200-
keys_under_root: true
201-
add_error_key: true
202-
message_key: log
200+
keys_under_root: true
201+
add_error_key: true
202+
message_key: log
203203
----
204204

205205
*`keys_under_root`*:: By default, the decoded JSON is placed under a "json" key
@@ -256,5 +256,5 @@ all containers under the default Kubernetes logs path:
256256
- "/var/log/containers/*.log"
257257
parsers:
258258
- container:
259-
stream: stdout
259+
stream: stdout
260260
----

0 commit comments

Comments
 (0)