fluent-plugin-multi-format-parser
fluent-plugin-multi-format-parser copied to clipboard
repeatedly
Multi format parser for Fluentd
I currently parse one tag with a simple filter but I need to add a different pattern to the filter and I'm planning to migrate to a multi_format plugin. My...
Can you please tell me how to use parse the tomcat logs(debus,error which is a multiline) and access logs from the stdout.. It will be helpfull if you share the...
My fluentd config has two regexes, but only the first one will match. This is my .conf file. ``` @type http port 8888 ## live debugging agent @type debug_agent bind...
Fluent.Conf ``` @type tail @label @tcpstream tag proxy.log path /fluentd/log/proxy-service-*.log pos_file /fluentd/log/fluentd_posfile.log.pos pos_file_compaction_interval 72h @type multi_format expression /^\[(?[^\]]*)\] (?[^ ]*) (?[^ ]*) (?\d*) (?\d*) $/ time_key logtime time_format %Y-%m-%d %H:%M:%S...
In multi_format, add diff value of keytype key for each pattern matched. ``` @type multi_format format /.*reg1.*/ #keytype type1 format /.*reg2.*/ #keytype type2 format json #keytype type3 ``` My purpose...
I am trying to use multiline parser within this plugin and It seems that doesnt work Ive tested it also with Java stack trace example from documentation... My configuration: ```...
The requirements are met but a dependency error occurs. -My env are as the following. Ruby: 2.0.0 Fluentd: 0.12.0 -I expected "ruby version 2.0.0" to be ok when i use...
Is it possible to set a pattern-specific tag? I'd like to tag based on which pattern matched the message. The examples in the [README](https://github.com/repeatedly/fluent-plugin-multi-format-parser/blob/master/README.md) show the tag being set at...
In the fluentd input, I am using a parser in the syslog input plugin to break the messages using regular expression. After the separation, I am trying to parse one...
Hi, Thanks for the great plugin! We may be attempting to configure it improperly esp. around the v0.14 changes, but are at a loss as to how to use ``...
