[
https://issues.apache.org/jira/browse/NIFI-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168426#comment-15168426
]
ASF GitHub Bot commented on NIFI-1420:
--------------------------------------
Github user trixpan commented on the pull request:
https://github.com/apache/nifi/pull/233#issuecomment-189112752
@bbende
Out of curiosity, why would someone use ListenSplunk instead of
ListenSyslog using TCP with Parsing disabled (aka poor man ListenTCP) ?
I was under the impression Splunk forwarder frame format when using non
indexed data is a pure TCP stream, pretty much like netcat. (Or are we going
to be able to acknowledge events as the Indexer does when communicating with
forwarders?)
If that is the case, shouldn't we call this ListenTCP instead of
ListenSplunkForwarder?
> Splunk Processors
> -----------------
>
> Key: NIFI-1420
> URL: https://issues.apache.org/jira/browse/NIFI-1420
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: 0.6.0
>
>
> To continue improving NiFi's ability to collect logs, a good integration
> point would be to have a processor that could listen for data from a Splunk
> forwarder (https://docs.splunk.com/Splexicon:Universalforwarder). Being able
> to push log messages to Splunk would also be useful.
> Splunk provides an SDK that may be helpful:
> https://github.com/splunk/splunk-sdk-java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
