Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1418
@scottcrespo thanks for the message.
the work around here is fairly simple in nature: to allow any beat
(filebeat, metricbeat, etc) to send their data directly into NiFi, allowing
people currently using logstash to seamlessly migrate data pipelines into NiFi.
When you read any beats doco you will note they have a few different
outputs: Kafka, ES and Logstash. This processor allows NiFi to act as a
destination of _*beats_ logstash output.
So in theory, your Metricbeat module could still use metricbeat as
underlying agent, but instead of shipping it directly into ES as I believe you
are planning to do, ship it to NiFi (so it can be further processed, persisted
in HDFS, etc)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
