[
https://issues.apache.org/jira/browse/NIFI-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822980#comment-15822980
]
ASF GitHub Bot commented on NIFI-3238:
--------------------------------------
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)
> ListenLumberjack should support the *beat protocol
> --------------------------------------------------
>
> Key: NIFI-3238
> URL: https://issues.apache.org/jira/browse/NIFI-3238
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Andre
> Assignee: Andre
>
> ListenLumberjack currently only supports v1 of the Lumberjack protocol. This
> version has been deprecated in favor of v2, which is used on *beat (e.g.
> filebeat, packetbeat, etc) edge components of the ELK stack.
> We should consider deprecating ListenLumberjack or to extend it to handle
> both v1 and v2 of the protocol.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
