logstash-filter-kv
logstash-filter-kv copied to clipboard
logstash-plugins
By prepending an optional, non-capturing field splitter to our scanning regexp we ensure that a valueless key is fully consumed, preventing a multibyte field splitter from partially leaking into the...
Use a handy DFA based algorithm to parse the input, when dealing with most naive configuration.
This fixes issue #43 which is a regression introduced into the kv filter v2.0.3 and above. Previously if an existing `target` field existed in the event, the kv fields were...
This resolves #2. The regex proposed in https://github.com/logstash-plugins/logstash-filter-kv/issues/2#issuecomment-137837605 turned out to not work correctly, and it was extremely slow (the test suite never finished). Instead, I adapted the regex from...
I didn't confirm this, but my suspicion is that the changes in the following commit seems to override any fields in the target object for the KV filter: [refactor field...
Hello, The current 'kv' module stores extracted keys and values in 'dotted' notation (some.prefix.key1 = value1, some.prefix.key2 = value2, ...) I would like to request that a variant of [this...
Migrated from JIRA: https://logstash.jira.com/browse/LOGSTASH-2272 which was replicated at https://github.com/elasticsearch/logstash/issues/1605 With the following config: ``` input { stdin { } } filter { kv { } } output { stdout {...
this request is to enable dynamic target (eg, field value or tag name) value, a la kv { target => "%{[some][crazy][field][or][tag]}" } parallel to json request: https://github.com/logstash-plugins/logstash-filter-json/issues/28
Hi, I can't split this string field : "rev=3&sid=" KV: ``` kv { enable_metric => false source => [ "[message]" ] target => "[test]" field_split => "&" value_split => "="...
Dear KV filter support, Can you please add support for the following string in a kv filter foo=bar(baz) as => foo=bar newvariable=baz or anything that is appropriate to be able...
