iridian-ks opened a new pull request #5452: URL: https://github.com/apache/camel/pull/5452
<!-- Uncomment and fill this section if your PR is not trivial - [ x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x ] Each commit in the pull request should have a meaningful subject line and body. - [x ] If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue. - [x ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x ] Run `mvn clean install -Psourcecheck` in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically. Below are the contribution guidelines: https://github.com/apache/camel/blob/main/CONTRIBUTING.md --> ### What this PR does? Added a headerOnly and bodyOnly options to the splunk-hec component. These options will filter down what is sent to Splunk instead of always sending everything. ### Why? Sending both headers and body to Splunk wrapped in a custom JSON object looks ugly and makes the data you need harder to find. For those who only need the body they can opt into only sending the body which will make it easier to find the log data and make SPL queries shorter. Also, sending less data should result in cheaper usage as Splunk charged per GB. For those who do want both headers and body but may want them in separate indicies there is also an option to only send headers to a separate index using a multicast(). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
