fluent-plugins-nursery / fluent-plugin-grepcounter Goto Github PK

I've got the following fluentd configuration:

  <source>
    type tail
    path /var/log/test.log
    pos_file fluentd-docker.pos
    time_format %Y-%m-%dT%H:%M:%S
    tag test.*
    format json
    read_from_head true
  </source>
  <match **>
    @type grepcounter
    count_interval 60
    input_key validkey
    regexp validvalue
    greater_equal 1
    add_tag_prefix tagprefix
  </match>
  <match **>
    @type stdout
  </match>

I'd expect that after inserting the following message:
echo '{"validkey": "validvalue"}' >> /var/log/test.log
into test.log file, the message is displayed in fluentd logs. However, it doesn't happen. When I remove grepcounter section, the message is correctly displayed.

Please correct me if I'm wrong - shouldn't it work in a way that grepcounter catches the message and emits a new message which is later caught by stdout?

Additional info:

# /opt/td-agent/embedded/bin/ruby --version
ruby 2.1.10p492 (2016-04-01 revision 54464) [x86_64-linux]

# /opt/td-agent/embedded/bin/gem list | grep fluent-plugin-grepcounter
fluent-plugin-grepcounter (0.6.0)

I've also tried with v0.5.0 - issue is the same.

add a parater to add some specifed keys to the count line..

config parameter
include_keys host,sessionid,......

for ex {"count":2,"message":[....],"host":["asp01","asp02",....],.......}

this will include the keys speciefed in the config and add them (usefull for application clusters)

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the gemspec of your last release.

via e.g.

spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']

Including a license in your gemspec is an easy way for rubygems.org and other tools to check how your gem is licensed. As you can imagine, scanning your repository for a LICENSE file or parsing the README, and then attempting to identify the license or licenses is much more difficult and more error prone. So, even for projects that already specify a license, including a license in your gemspec is a good practice. See, for example, how rubygems.org uses the gemspec to display the rails gem license.

There is even a License Finder gem to help companies/individuals ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec. This is an important enough issue that even Bundler now generates gems with a default 'MIT' license.

I hope you'll consider specifying a license in your gemspec. If not, please just close the issue with a nice message. In either case, I'll follow up. Thanks for your time!

Appendix:

If you need help choosing a license (sorry, I haven't checked your readme or looked for a license file), GitHub has created a license picker tool. Code without a license specified defaults to 'All rights reserved'-- denying others all rights to use of the code.
Here's a list of the license names I've found and their frequencies

p.s. In case you're wondering how I found you and why I made this issue, it's because I'm collecting stats on gems (I was originally looking for download data) and decided to collect license metadata,too, and make issues for gemspecs not specifying a license as a public service :). See the previous link or my blog post about this project for more information.

It doesn't seem to work for me and I'd like to understand if I'm doing something wrong or if the issue is with the plugin.

Hi,
this plugin is able to accept a regular expression syntax instead of strings?
Best Regards.