fluent-plugin-grep

Fluentd plugin to grep messages.

Configuration

<match foo.bar.**>
  type grep
  regexp1 message WARN
  exclude1 message favicon
  add_tag_prefix greped
</source>

Assuming following inputs are coming:

foo.bar: {"foo":"bar","message":"2013/01/13T07:02:11.124202 INFO GET /ping"}
foo.bar: {"foo":"bar","message":"2013/01/13T07:02:13.232645 WARN POST /auth"}
foo.bar: {"foo":"bar","message":"2013/01/13T07:02:21.542145 WARN GET /favicon.ico"}
foo.bar: {"foo":"bar","message":"2013/01/13T07:02:43.632145 WARN POST /login"}

then output bocomes as belows (like, | grep WARN | grep -v favicon):

greped.foo.bar: {"foo":"bar","message":"2013/01/13T07:02:13.232645 WARN POST /auth"}
greped.foo.bar: {"foo":"bar","message":"2013/01/13T07:02:43.632145 WARN POST /login"}

Parameters

• regexp[1-20] field_key regexp

  The target field key and the filtering regular expression to grep out.

• exclude[1-20] field_key regexp

  The target field key and the excluding regular expression like grep -v

• tag

  The output tag name

• add_tag_prefix

  Add tag prefix for output message

• remove_tag_prefix

  Remove tag prefix for output message

• replace_invalid_sequence

  Replace invalid byte sequence in UTF-8 with '?' character if true

• input_key field_key (obsolete)

  The target field key to grep out. Use with regexp or exclude.

• regexp regexp (obsolete)

  The filtering regular expression

• exclude regexp (obsolete)

  The excluding regular expression like grep -v

ChangeLog

See CHANGELOG.md for details.

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

Copyright

Copyright (c) 2013 Naotoshi SEO. See LICENSE for details.