[
https://issues.apache.org/jira/browse/NIFI-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180536#comment-15180536
]
ASF GitHub Bot commented on NIFI-1420:
--------------------------------------
Github user bbende commented on the pull request:
https://github.com/apache/nifi/pull/233#issuecomment-192466857
@JPercivall Pushed up another commit that addresses the additional comments
from today.
Part of this change I decided to go the route that @trixpan suggested and
change ListenSplunkForwarder to ListenTCP, and as a result moved it to the
standard bundle. This will open it up to a lot more use cases and it wasn't
really Splunk specific. As a result I decided to take out the mime.type
attribute since it is writing bytes to FlowFiles and may not really be
text/plain all the time.
Let me know if anything else needs updating or was left out.
> 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)
