[
https://issues.apache.org/jira/browse/NIFI-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170732#comment-15170732
]
ASF GitHub Bot commented on NIFI-1420:
--------------------------------------
Github user trixpan commented on the pull request:
https://github.com/apache/nifi/pull/233#issuecomment-189735776
@bbende
The protocol is proprietary
https://answers.splunk.com/answers/12543/splunk-data-format.html
so unless they suddenly decided to document it the ListenSplunk will
continue be a ListenTCP (hence my previous comments).
I am quite picky on this one as certain Splunk SE teams seem to have this
culture of demotivating the use of TCP forwarding as an "unfair" use of their
proprietary IP (technically speaking - legal is gray area - you can in fact
use splunk forwarder as a "miNiFi"-like agent and as long you don't send data
into tge indexers your licence will not be consumed).
> 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)
