https://github.com/banyan/fluent-plugin-filter_keys

Filter if a specific key is present or not in event logs
https://github.com/banyan/fluent-plugin-filter_keys

Last synced: 16 days ago
JSON representation

Filter if a specific key is present or not in event logs

• Host: GitHub
• URL: https://github.com/banyan/fluent-plugin-filter_keys
• Owner: banyan
• License: mit
• Created: 2013-03-30T07:37:54.000Z (almost 12 years ago)
• Default Branch: master
• Last Pushed: 2018-12-02T04:17:19.000Z (about 6 years ago)
• Last Synced: 2025-01-02T12:38:19.910Z (about 1 month ago)
• Language: Ruby
• Homepage:
• Size: 12.7 KB
• Stars: 9
• Watchers: 4
• Forks: 2
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
# fluent-plugin-filter_keys

[![Build Status](https://secure.travis-ci.org/banyan/fluent-plugin-filter_keys.png)](http://travis-ci.org/banyan/fluent-plugin-filter_keys)

## Overview

[Fluentd](http://fluentd.org) plugin to filter if a specific key is present or not in event logs.

## Installation

```

$ gem install fluent-plugin-filter_keys

```

## Configuration

```

  type filter_keys

  add_tag_prefix filter_keys.

  ensure_keys    foo, bar

  type filter_keys

  add_tag_prefix filter_keys.

  denied_keys    foo, bar

```

#### ensure_keys

Keys to be existed in a event log. If it doesn't match, the event log will be discarded.

#### denied_keys

Keys to be not existed in a event log. If it matches, the event log will be discarded.

#### add_tag_and_reemit

Default false. if this configure parameter is true and doesn't match keys, add tag 'discarded' and reemit.

## 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