[
https://issues.apache.org/jira/browse/NIFI-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178781#comment-15178781
]
ASF GitHub Bot commented on NIFI-1420:
--------------------------------------
Github user bbende commented on the pull request:
https://github.com/apache/nifi/pull/233#issuecomment-192008077
@JPercivall I pushed up three commits, one for each processor, that I
believe address all your comments/suggestions. Let me know if anything is
missing or not addressed.
Regarding the UDP issue you saw, this only appears to be an issue when
selecting the source type as misc_text and I believe this is something more on
the side of sending the appropriate data to appropriate index type. When I send
syslog messages to a syslog type over UDP it works fine.
Regarding the SSL issue you saw, I can't explain how Splunk was able to
accept the encrypted data in your case, but I did create a tcp-ssl input type
in the local inputs.conf and was able to send data to it and have it show up
normal in Splunk, so I think that is the intended use case. I don't see a way
to make TCP inputs with SSL through the UI.
> 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)
