Added new high performance HTTP Event Collector (HEC) output adaptor.#3
Added new high performance HTTP Event Collector (HEC) output adaptor.#3damiendallimore wants to merge 1 commit into
Conversation
Refactored SplunkEvent class to produce simple JSON event.
|
Hello, @damiendallimore ! Sorry for delay. We were enough busy with releases for SI core project and other related. |
There was a problem hiding this comment.
Minor, of course, but that would be better to configure the IDE to add an new line in the end of file.
At least, to avoid such a comments in the future 😄
|
So, from big height that's all. I'd prefer do not do so much re-work myself, because it is your PR, but if you don't have enough time to bring it into mind, that works for us, too. Thank you for the contribution one more time! |
|
Closed in favor of #5 . Thank you for the contribution and looking forward for more! |
With the recent release of Splunk version 6.3 we now have a new high performance data collector called the HTTP Event Collector (HEC), http://blogs.splunk.com/2015/10/06/http-event-collector-your-direct-event-pipe-to-splunk-6-3/
This should now be used over our legacy data collectors which have been available as output adaptors in Spring Integration for some time.
This pull request contains a new output integration adaptor for sending events to Splunk via HEC.
I also refactored the SplunkEvent class which was riddled with legacy logic that is now irrelevant.I also updated the output of the SplunkEvent class to produce simple JSON which is more optimal that KV pairs for Splunk.
Damien Dallimore (Developer Evangelist @ Splunk , ddallimore@splunk.com)
I have signed and agree to the terms of the SpringSource Individual
Contributor License Agreement.