Beats direction: ingest pipeline vs. local input modifications

When using a filebeat module, some data manipulations seem to be done in two places:

  1. In an ingest pipeline
  2. in filebeat at input using filebeat/module/[modulename]/[module-sub]/config/...yml.

This seems to be opposite the idea of keeping the beat as light weight as possible.
And it seems to add complexity or confusion as to what data is adjust where.

My questions are:

  1. Why is the data manipulation split?
  2. Is this divergence a target direction or just sign of migrating to ingest with the goal for everything to be an ingest eventually?
  3. Is there any current easy and bulk way to replicate the local filbeat input transformations into ingest pipelines?

Appreciate any insight here.

  • jessvin

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.