[
https://issues.apache.org/jira/browse/NIFI-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-7801:
-----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add acknowledgement check to Splunk
> -----------------------------------
>
> Key: NIFI-7801
> URL: https://issues.apache.org/jira/browse/NIFI-7801
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Simon Bence
> Assignee: Simon Bence
> Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Currently there is no proper way to utilise HTTP Event Collector Indexer
> Acknowledgment functionality when sending data into Splunk. It would be
> beneficial to extend current functionality with the client side handling of
> this capability.
> There are multiple possible approaches, like:
> * Extend PutSplunk with HTTP protocol (downside: the current behaviour does
> not really fits with adding HTTP support)
> * Extend InvokeHTTP with (downside: this is not a Splunk specific processor)
> * Adding a new processor, PutSplunkHTTP
> Adding a new, specific processor with limited possibilities for customise
> HTTP requests and the capability to "follow up" on acknowledgements looks
> like viable approach. The highlights are:
> * The processor should send incoming flowfile content to Splunk, in similar
> fashion as PutSplunk behaves
> * This should happen via HTTP protocol
> * The processor must support channel and channel id
> * The processor should store incoming ackId-s
> * There should be a mechanism polling ackId-s and based on the Splunk's
> answer (or possible timeout) it should manage this collection of ids. Based
> on the outcome, the processor should emit on the an appropriate relationship.
> From Splunk side, this is the initial expectation:
> https://docs.splunk.com/Documentation/Splunk/8.0.5/Data/AboutHECIDXAck
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
