We use file beat extensively to capture exception in the log files. We define all the error pattern inside the include_lines in the prospector section in array. This can identify the error pattern and using multi line it aggregates errors lines and sends me the event.
However, the info about which pattern is matched currently from the array of patterns is not shown in the result. It would be nice to show matched_pattern value in the output when include_lines is used.
I also understand when RegEx is used to match we cannot output any match pattern.
when it outputs, i expect filebeat to include attribute like "mattched_pattern":"ERROR" or "mattched_pattern":"WARN"... since each events will be matched based on this include_lines.....
currently it outputs only message attribute, which gives the complete error detail.. but i cant identify which pattern matched from the list....
Yes, I think this is not possible with filebeat, as we don't normally do processing on messages, but shipping. You need to use Logstash for this, take a look to the given documentation
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.