fluent-plugin-parser
fluent-plugin-parser copied to clipboard
With these vertsions... ``` root@nodens:/etc/td-agent/config.d# td-agent-gem list fluent *** LOCAL GEMS *** fluent-config-regexp-type (1.0.0) fluent-diagtool (1.0.1) fluent-logger (0.9.0) fluent-plugin-calyptia-monitoring (0.1.3) fluent-plugin-elasticsearch (5.2.3, 5.2.2) fluent-plugin-flowcounter-simple (0.1.0) fluent-plugin-kafka (0.17.5) fluent-plugin-metrics-cmetrics (0.1.2) fluent-plugin-opensearch...
see also https://github.com/fluent/fluentd/pull/1733/files
Can I use this plugin's output with multiline format for logging Rails requests?
td-agent : 0.12.35 regex: ``` regex (?[\w-]+)\s*(?[\w\/]+)\[(?[\d]+)\]\:\s*(?[\w]{10}):\s*to=,\s*relay=(?[^,]+),\s*delay=(?[^,]+),\s*delays=(?[^,]+),\s*dsn=(?[^,]+),\s*status=(?[\w]+)\s*\((?(.*))\) ``` match text: `Jul 5 11:28:29 web-niemiao-3 postfix/smtp[17563]: AE03562521: to=, relay=alt1.gmail-smtp-in.l.google.com[74.125 .30.27]:25, delay=2.9, delays=0.02/0/2.3/0.53, dsn=4.7.0, status=deferred (host alt1.gmail-smtp-in.l.google.com[74.125.30.27] said: 421 -4.7.0 [122.14.62.30 15]...
Add problem explanation for v0.14.
Will be good when format not match, I can apply another tag, e.g. ``` type parser key_name message format /myregex/ unmatched_tag my.app.unknown ``` then I can have another chained match:...
This adds an option to prefix the existing record. E.g., input like: `{"message":"a:A b:B c:C","source":"xyz"}` with config as: ``` type parser format ltsv reserve_data yes reserve_data_prefix @ ``` becomes ```...