mirror of
https://github.com/elastic/logstash.git
synced 2025-04-24 06:37:19 -04:00
Add comments to explain 'negate' in multiline filters
This commit is contained in:
parent
7c67be2ba8
commit
f48488d051
1 changed files with 5 additions and 0 deletions
|
@ -17,6 +17,7 @@ class LogStash::Filters::Multiline < LogStash::Filters::Base
|
|||
# - multiline:
|
||||
# <type>:
|
||||
# pattern: <regexp>
|
||||
# negate: true
|
||||
# what: next
|
||||
# <type>
|
||||
# pattern: <regexp>
|
||||
|
@ -28,6 +29,10 @@ class LogStash::Filters::Multiline < LogStash::Filters::Base
|
|||
# The 'what' must be "previous" or "next" and indicates the relation
|
||||
# to the multi-line event.
|
||||
#
|
||||
# The 'negate' can be "true" or "false" (defaults false). If true, a
|
||||
# message not matching the pattern will constitute a match of the multiline
|
||||
# filter and the what will be applied. (vice-versa is also true)
|
||||
#
|
||||
# For example, java stack traces are multiline and usually have the message
|
||||
# starting at the far-left, then each subsequent line indented. Do this:
|
||||
#
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue