regexp
Last updated
Was this helpful?
Last updated
Was this helpful?
The regexp
parser plugin parses logs by given regexp pattern. The regexp must have at least one named capture (?<NAME>
PATTERN). If the regexp has a capture named time
, this is configurable via time_key
parameter, it is used as the time of the event. You can specify the time format using the time_format
parameter.
See for common parameters.
expression
regexp
required parameter
1.2.0
Specifies the regular expression for matching logs. Regular expression also supports i
and m
suffix.
i
(ignorecase)Ignores case in matching.
m
(multiline)Build regular expression as a multiline mode. .
matches the newline. See Ruby's .
both
Specifies both i
and m
.
expression
is the string type before 1.2.0.
ignorecase
bool
false
0.14.2
Ignores case in matching. Use i
option with expression.
Deprecated since 1.2.0. Use expression /pattern/i
instead.
multiline
bool
false
0.14.2
Deprecated since 1.2.0. Use expression /pattern/m
instead.
With this configuration:
This incoming event:
is parsed as:
Builds regular expression in multiline mode. .
matches the newline. See Ruby's . Use m
option with expression.
helps your regexp testing. Another way, is a great website to test your regexp for Fluentd configuration.
NOTE: You may hit Application Error at Fluentular due to . Retry a few hours later or use fluentd-ui
instead.
If this article is incorrect or outdated, or omits critical information, please . is an open-source project under . All components are available under the Apache 2 License.