Feature Request
Proposal: Enable the Telegraf to span regex patterns beyond one text line.
In other words the regex should be able to continue beyond the line breaks until it finds a predefined "line end" (or "new log line") regex pattern.
Note: the grok parser and the the log tail implementation currently used, are capable of that).
Current behavior:
Currently Telegraf can only apply regex patterns inside each text line in a log file.
Desired behavior:
To support an option where the log is broken into individual records fully by virtue of regex and without taking into account the line breaks (like in Log Stash and FluentD).
Use case:
Then the Telegraf can be freely used as a replacement for FluentD and/or LogStash when preferred.
That is especially desirable when InfluxDB is used as a consolidated log storage.
Feature Request
Proposal: Enable the Telegraf to span regex patterns beyond one text line.
In other words the regex should be able to continue beyond the line breaks until it finds a predefined "line end" (or "new log line") regex pattern.
Note: the grok parser and the the log tail implementation currently used, are capable of that).
Current behavior:
Currently Telegraf can only apply regex patterns inside each text line in a log file.
Desired behavior:
To support an option where the log is broken into individual records fully by virtue of regex and without taking into account the line breaks (like in Log Stash and FluentD).
Use case:
Then the Telegraf can be freely used as a replacement for FluentD and/or LogStash when preferred.
That is especially desirable when InfluxDB is used as a consolidated log storage.