filebeat/module/yourmodule/yourfileset/config/yourfileset.yml is the file which includes multiline configuration. Where yourmodule is the name of your module and yourfileset is the name of your fileset.
If your pipeline is in the standard place, it will load automatically. However, it is not there, you can configure it in the manifest.yml.
To generate required files, you need to call make update. After it is generated, Filebeat loads it automatically on startup.
thanks, I think I did that all, but maybe with intermediate steps.
So far it wont eat all lines (only the first) after the negated regex.
Will setup a dev elastic environment and do it like that in one go and see if it works out like that.
ok the multiline is ok now. But I have another issue, I can open a new thread or just ask: the make update creates a template for the fields, but there is also _meta/fields.yml and it seems those fields get added too!?
Short: how/where to place the fields for my module, and how to add them to the template to be created inside the index(pattern)?
Edit> so adding the new fields to _meta/fields.yml is enough, filebeat adds these to the index/template automagically.
I will do some more tests when done @kvch: where is the best place to propose new modules/comunity beats?
Well mine is more an example, there are some prework to do adopting my verbose gc log parser to another java version or gc type (the output pattern my differ)
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.