This patch is my attempt to prevent a class of issues reported by #515.
Problem
Right now, Fluentd assumes that a match pattern with a leading slash
is written in the regex notation (something like "/foo/").
This can lead to a confusing result if a user naively sets a file path
as a pattern. For example, the following configuration will be parsed
to RegExp(//), not RegExp(/var/log/):
<regexp>
key "path"
pattern /home
</regexp>
Solution
This patch adds a small note to describe how to specify such patterns properly.
This patch is my attempt to prevent a class of issues reported by #515.
Problem
Right now, Fluentd assumes that a match pattern with a leading slash is written in the regex notation (something like "/foo/").
This can lead to a confusing result if a user naively sets a file path as a pattern. For example, the following configuration will be parsed to
RegExp(//), notRegExp(/var/log/):Solution
This patch adds a small note to describe how to specify such patterns properly.