apupier opened a new pull request, #25777: URL: https://github.com/apache/camel/pull/25777
The `camel-splunk` component was deprecated in 4.19. The Splunk Java SDK it depends on is no longer actively maintained. Users who only need to **send events to Splunk** can migrate to `camel-splunk-hec`, which uses the Splunk HTTP Event Collector (HEC) over standard HTTPS with no dependency on the Splunk Java SDK. However, `camel-splunk-hec` is a **producer-only** component. The following `camel-splunk` capabilities have no equivalent in `camel-splunk-hec`: * **Consumer (search)**: normal searches, real-time searches, and saved-search execution are not supported. * **TCP streaming**: the `tcp` producer publish type (raw socket streaming to a Splunk TCP input) is not available. * **SUBMIT and STREAM publish types**: only HEC-based ingestion is supported. If your routes only produce events to Splunk (using the `submit` or `stream` publish types), switching to `camel-splunk-hec` is straightforward — configure the HEC token, index, sourceType, and source on the endpoint. If your routes consume (search) data from Splunk, there is currently no direct replacement within Apache Camel, and you will need to use the Splunk REST API directly or keep using `camel-splunk` until it is removed. NOTE: `camel-splunk-hec` is NOT deprecated and remains actively maintained. # Description <!-- - Write a pull request description that is detailed enough to understand what the pull request does, how, and why. --> # Target - [ ] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [ ] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). <!-- # *Note*: trivial changes like, typos, minor documentation fixes and other small items do not require a JIRA issue. In this case your pull request should address just this issue, without pulling in other changes. --> # Apache Camel coding standards and style - [ ] I checked that each commit in the pull request has a meaningful subject line and body. <!-- 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. --> - [ ] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. <!-- You can run the aforementioned command in your module so that the build auto-formats your code. This will also be verified as part of the checks and your PR may be rejected if if there are uncommited changes after running `mvn clean install -DskipTests`. You can learn more about the contribution guidelines at https://github.com/apache/camel/blob/main/CONTRIBUTING.md --> # AI-assisted contributions - [ ] If this PR includes AI-generated code, commits have proper co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR description identifies the AI tool used. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
