This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git


The following commit(s) were added to refs/heads/main by this push:
     new 78de7f506 chore: the FHIR, OGC API, Splunk HEC and SNMP Kamelets take 
timeouts and more endpoint options (#3170) (#3228)
78de7f506 is described below

commit 78de7f5067f2e028b57240731822fd52ba887625
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Nov 18 22:35:54 2026 +0100

    chore: the FHIR, OGC API, Splunk HEC and SNMP Kamelets take timeouts and 
more endpoint options (#3170) (#3228)
    
    fhir-sink takes connectionTimeout, socketTimeout, compress, summary and
    validationMode. fhir-source takes delay, accessToken and an HTTP proxy
    (proxyHost, proxyPort, proxyUser, proxyPassword); its username and
    password are no longer required, so it works with a server without login
    and with an access token alone (with both set, HAPI sends two
    Authorization headers). ogcapi-features-action takes connectTimeout and
    responseTimeout.
    splunk-hec-sink takes splunkEndpoint, to send to the raw endpoint.
    snmp-source takes snmpTimeout (mapped to the timeout option of the
    component, as timeout is taken by the kamelet: component), retries,
    initialDelay and snmpContextName.
    
    All new options are optional placeholders without a default, so with
    them unset the endpoint URIs are the same as before. Secrets go into
    RAW(); splunkEndpoint and snmpContextName have a pattern.
    
    nominatim-geocode-action gets no language option: the Nominatim producer
    of the Camel geocoder component does not use its language option, so
    this needs a Camel change first.
    
    Each option was checked against HAPI FHIR, Splunk with HEC, net-snmp and
    a recording HTTP server; the descriptions and the partial pages say what
    the tests showed.
    
    Co-authored-by: Claude Opus 5.5 <[email protected]>
---
 .../ROOT/partials/fhir-sink-description.adoc       | 31 ++++++++++++++++
 .../ROOT/partials/fhir-source-description.adoc     | 32 +++++++++++++++-
 .../ogcapi-features-action-description.adoc        | 27 ++++++++++++++
 .../ROOT/partials/snmp-source-description.adoc     | 34 +++++++++++++++++
 .../ROOT/partials/splunk-hec-sink-description.adoc | 26 ++++++++++++-
 kamelets/fhir-sink.kamelet.yaml                    | 29 ++++++++++++++-
 kamelets/fhir-source.kamelet.yaml                  | 43 +++++++++++++++++++---
 kamelets/ogcapi-features-action.kamelet.yaml       | 15 +++++++-
 kamelets/snmp-source.kamelet.yaml                  | 27 +++++++++++++-
 kamelets/splunk-hec-sink.kamelet.yaml              |  9 ++++-
 .../main/resources/META-INF/kamelets-index.json    | 10 ++---
 .../main/resources/kamelets/fhir-sink.kamelet.yaml | 29 ++++++++++++++-
 .../resources/kamelets/fhir-source.kamelet.yaml    | 43 +++++++++++++++++++---
 .../kamelets/ogcapi-features-action.kamelet.yaml   | 15 +++++++-
 .../resources/kamelets/snmp-source.kamelet.yaml    | 27 +++++++++++++-
 .../kamelets/splunk-hec-sink.kamelet.yaml          |  9 ++++-
 16 files changed, 378 insertions(+), 28 deletions(-)

diff --git a/docs/modules/ROOT/partials/fhir-sink-description.adoc 
b/docs/modules/ROOT/partials/fhir-sink-description.adoc
index 461310742..719fd32ec 100644
--- a/docs/modules/ROOT/partials/fhir-sink-description.adoc
+++ b/docs/modules/ROOT/partials/fhir-sink-description.adoc
@@ -22,6 +22,37 @@ Supports multiple authentication methods:
 - OAuth 2.0 access tokens
 - Basic authentication with username and password
 
+=== Timeouts, Compression and Summary
+
+The connection to the server, and the answer to each request, each time out 
after 10 seconds unless
+`connectionTimeout` and `socketTimeout` say otherwise. `compress` sends the 
resource compressed with GZIP.
+`summary` asks the server for a short answer, with the FHIR `_summary` 
parameter; the server still stores the whole
+resource. `validationMode` `NEVER` skips the read of `/metadata` before the 
first message, for a server that does
+not serve it.
+
+[source,yaml,subs='+attributes,macros']
+----
+- route:
+    from:
+      uri: "kamelet:kafka-source"
+      parameters:
+        topic: "admissions"
+        bootstrapServers: "localhost:9092"
+      steps:
+        - to:
+            uri: "kamelet:fhir-sink"
+            parameters:
+              serverUrl: "https://fhir.example.com/fhir";
+              apiName: "CREATE"
+              methodName: "resource"
+              accessToken: "my-oauth-token"
+              connectionTimeout: 5000
+              socketTimeout: 60000
+              compress: true
+              summary: "TRUE"
+              validationMode: "NEVER"
+----
+
 === Proxy Support
 
 The Kamelet can be configured to work through HTTP proxies with optional 
authentication.
diff --git a/docs/modules/ROOT/partials/fhir-source-description.adoc 
b/docs/modules/ROOT/partials/fhir-source-description.adoc
index 8e38e4f93..c5aa07851 100644
--- a/docs/modules/ROOT/partials/fhir-source-description.adoc
+++ b/docs/modules/ROOT/partials/fhir-source-description.adoc
@@ -2,7 +2,11 @@
 
 === Authentication
 
-This Kamelet requires username and password authentication to access the FHIR 
server. The credentials are configured through the `username` and `password` 
properties.
+Log in to the FHIR server with Basic authentication, through the `username` 
and `password` properties, or with an
+OAuth access token in `accessToken`. Leave them out for a server without 
login. When both are set, both are sent.
+
+To reach the server through an HTTP proxy, set `proxyHost` and `proxyPort`, 
and `proxyUser` and `proxyPassword` for
+a proxy that needs a login.
 
 === Configuration
 
@@ -13,6 +17,7 @@ The FHIR Source Kamelet supports the following configurations:
 - **Encoding**: Response encoding format - JSON or XML (default: "JSON")
 - **FHIR Version**: The FHIR specification version to use (default: "R4")
 - **Pretty Print**: Whether to format JSON responses for readability (default: 
true)
+- **Delay**: How long to wait between two searches, in milliseconds (default: 
500)
 
 === Output Format
 
@@ -57,4 +62,27 @@ The Kamelet outputs data in JSON format, marshalling FHIR 
resources according to
             uri: "kamelet:log-sink"
 ----
 
-This example searches for Observation resources from the FHIR server with 
compact JSON output.
\ No newline at end of file
+This example searches for Observation resources from the FHIR server with 
compact JSON output.
+
+=== Example with an Access Token, a Proxy and a Delay
+
+[source,yaml,subs='+attributes,macros']
+----
+- route:
+    from:
+      uri: "kamelet:fhir-source"
+      parameters:
+        serverUrl: "https://fhir.example.com/fhir";
+        accessToken: "my-oauth-token"
+        url: "/Observation?_lastUpdated=gt2026-01-01"
+        delay: 60000
+        proxyHost: "proxy.example.com"
+        proxyPort: 3128
+        proxyUser: "proxy-user"
+        proxyPassword: "proxy-password"
+      steps:
+        - to:
+            uri: "kamelet:log-sink"
+----
+
+This example runs the search once a minute, through an HTTP proxy, with an 
OAuth access token.
diff --git a/docs/modules/ROOT/partials/ogcapi-features-action-description.adoc 
b/docs/modules/ROOT/partials/ogcapi-features-action-description.adoc
new file mode 100644
index 000000000..7de677e95
--- /dev/null
+++ b/docs/modules/ROOT/partials/ogcapi-features-action-description.adoc
@@ -0,0 +1,27 @@
+== OGC API Features Action Kamelet Description
+
+=== Timeouts
+
+`connectTimeout` limits how long to wait for the connection to the service, 
and `responseTimeout` how long to wait
+for its answer, both in milliseconds. A service that does not answer in time 
fails the message. When they are not
+set, the answer is awaited for up to 3 minutes.
+
+[source,yaml,subs='+attributes,macros']
+----
+- route:
+    from:
+      uri: "kamelet:timer-source"
+      parameters:
+        period: 60000
+        message: ""
+      steps:
+        - to:
+            uri: "kamelet:ogcapi-features-action"
+            parameters:
+              url: "https://features.example.com/ogcapi";
+              collection: "lakes"
+              connectTimeout: 5000
+              responseTimeout: 30000
+        - to:
+            uri: "kamelet:log-sink"
+----
diff --git a/docs/modules/ROOT/partials/snmp-source-description.adoc 
b/docs/modules/ROOT/partials/snmp-source-description.adoc
index b5844463a..9ddb51658 100644
--- a/docs/modules/ROOT/partials/snmp-source-description.adoc
+++ b/docs/modules/ROOT/partials/snmp-source-description.adoc
@@ -15,3 +15,37 @@ the wire.
 
 Prefer `snmpVersion` 3 where the device supports it. `securityLevel` defaults 
to 3
 (authPriv), which gives both authentication and privacy.
+
+=== Timeouts and Retries
+
+A device that does not answer a poll gives no message. The poll is sent again 
`retries` times, each time after
+waiting `snmpTimeout` milliseconds for the answer: 2 more times, after 1.5 
seconds each, when they are not set. The
+first poll starts `initialDelay` milliseconds after the integration starts, 
one second when it is not set.
+
+=== Example with an SNMP v3 Context
+
+A device that serves several sets of values under one address, such as one per 
virtual router, names each set a
+context. With SNMP v3, `snmpContextName` reads the values of one context.
+
+[source,yaml,subs='+attributes,macros']
+----
+- route:
+    from:
+      uri: "kamelet:snmp-source"
+      parameters:
+        host: "192.168.1.1"
+        oids: "1.3.6.1.2.1.1.3.0"
+        delay: 60000
+        initialDelay: 10000
+        snmpTimeout: 5000
+        retries: 0
+        snmpVersion: 3
+        securityName: "monitor"
+        securityLevel: 2
+        authenticationProtocol: "SHA1"
+        authenticationPassphrase: "my-passphrase"
+        snmpContextName: "vrf-blue"
+      steps:
+        - to:
+            uri: "kamelet:log-sink"
+----
diff --git a/docs/modules/ROOT/partials/splunk-hec-sink-description.adoc 
b/docs/modules/ROOT/partials/splunk-hec-sink-description.adoc
index a6ae4c984..3f2106a78 100644
--- a/docs/modules/ROOT/partials/splunk-hec-sink-description.adoc
+++ b/docs/modules/ROOT/partials/splunk-hec-sink-description.adoc
@@ -40,4 +40,28 @@ Ideal for sending various types of data to Splunk for:
 - Metrics and performance monitoring
 - Security event correlation
 - Business intelligence and reporting
-- Machine learning and anomaly detection
\ No newline at end of file
+- Machine learning and anomaly detection
+
+=== Event and Raw Endpoints
+
+By default the Kamelet sends to the event endpoint, 
`/services/collector/event`, and Splunk takes the index, the
+source and the source type of each event from `index`, `source` and 
`sourceType`. With `splunkEndpoint` set to
+`/services/collector/raw`, Splunk stores the whole JSON object that the 
Kamelet sends as the raw text of the event.
+The index, the source and the source type then come from the token, or from 
query parameters on the path:
+
+[source,yaml,subs='+attributes,macros']
+----
+- route:
+    from:
+      uri: "kamelet:timer-source"
+      parameters:
+        period: 10000
+        message: "hello"
+      steps:
+        - to:
+            uri: "kamelet:splunk-hec-sink"
+            parameters:
+              splunkUrl: "my_server.splunkcloud.com:8088"
+              token: "12345678-1234-1234-1234-123456789012"
+              splunkEndpoint: 
"/services/collector/raw?index=main&sourcetype=_json"
+----
diff --git a/kamelets/fhir-sink.kamelet.yaml b/kamelets/fhir-sink.kamelet.yaml
index 33fabbde1..a64154848 100644
--- a/kamelets/fhir-sink.kamelet.yaml
+++ b/kamelets/fhir-sink.kamelet.yaml
@@ -40,7 +40,7 @@ spec:
 
       Output: when it is used inside a route, the body afterwards is the 
outcome of the operation, as a Java object of the HAPI FHIR library, with the 
id of the resource; it is not JSON.
 
-      Good to know: a body that is not a valid FHIR resource of the chosen 
`fhirVersion` fails the message. Operations that do not take a resource, such 
as `READ` or `SEARCH`, fail.
+      Good to know: a body that is not a valid FHIR resource of the chosen 
`fhirVersion` fails the message. Operations that do not take a resource, such 
as `READ` or `SEARCH`, fail. Before the first message, it reads the capability 
statement of the server at `/metadata`, unless `validationMode` is `NEVER`. A 
server that does not answer within `connectionTimeout` and `socketTimeout`, 10 
seconds each when they are not set, fails the message.
     required:
     - serverUrl
     - apiName
@@ -89,6 +89,31 @@ spec:
         description: "If true, the connection to the server is set up at the 
first message instead of when the integration starts, so that the integration 
can start while the server is not reachable. The first message then takes a 
little longer."
         type: boolean
         default: false
+      connectionTimeout:
+        title: Connection Timeout
+        description: How long to wait for the connection to the server to be 
set up, in milliseconds. When it is not set, it is 10000 (10 seconds). A server 
that cannot be reached in time fails the message.
+        type: integer
+        example: 5000
+      socketTimeout:
+        title: Socket Timeout
+        description: How long to wait for the answer of the server to a 
request, in milliseconds. When it is not set, it is 10000 (10 seconds). A 
server that does not answer in time fails the message, so raise it for a slow 
server.
+        type: integer
+        example: 60000
+      compress:
+        title: Compress
+        description: If true, the resource sent to the server is compressed 
with GZIP, with the header `Content-Encoding` set to `gzip`, which saves 
bandwidth for large resources. The server must accept GZIP requests.
+        type: boolean
+        example: true
+      summary:
+        title: Summary
+        description: Asks the server to answer with a short form of the 
resource, with the FHIR `_summary` parameter on every request, such as `TRUE` 
for the summary elements only, or `DATA` for all but the text. The server still 
stores the whole resource; only the answer, the body afterwards, is shorter. 
When it is not set, the server answers in full.
+        type: string
+        enum: ["COUNT", "TEXT", "DATA", "TRUE", "FALSE"]
+      validationMode:
+        title: Validation Mode
+        description: Whether the capability statement of the server, at 
`/metadata`, is read before the first message. With `ONCE`, a server that does 
not answer it fails the message; `NEVER` does not read it, for a server without 
`/metadata`. When it is not set, it is `ONCE`.
+        type: string
+        enum: ["NEVER", "ONCE"]
       proxyHost:
         title: Proxy Host
         description: The host name of an HTTP proxy to reach the server 
through. Use it with `proxyPort`.
@@ -159,4 +184,4 @@ spec:
                         prettyPrint: "{{prettyPrint}}"
                         fhirVersion: "{{fhirVersion}}"
         - to:
-            uri: 
"fhir://{{apiName}}/{{methodName}}?accessToken=RAW({{?accessToken}})&encoding={{encoding}}&fhirVersion={{fhirVersion}}&inBody=resource&lazyStartProducer={{lazyStart}}&log={{log}}&password=RAW({{?password}})&prettyPrint={{prettyPrint}}&proxyHost={{?proxyHost}}&proxyPassword=RAW({{?proxyPassword}})&proxyPort={{?proxyPort}}&proxyUser=RAW({{?proxyUser}})&serverUrl={{serverUrl}}&username=RAW({{?username}})"
+            uri: 
"fhir://{{apiName}}/{{methodName}}?accessToken=RAW({{?accessToken}})&compress={{?compress}}&connectionTimeout={{?connectionTimeout}}&encoding={{encoding}}&fhirVersion={{fhirVersion}}&inBody=resource&lazyStartProducer={{lazyStart}}&log={{log}}&password=RAW({{?password}})&prettyPrint={{prettyPrint}}&proxyHost={{?proxyHost}}&proxyPassword=RAW({{?proxyPassword}})&proxyPort={{?proxyPort}}&proxyUser=RAW({{?proxyUser}})&serverUrl={{serverUrl}}&socketTimeout={{?socketTimeout}}&s
 [...]
diff --git a/kamelets/fhir-source.kamelet.yaml 
b/kamelets/fhir-source.kamelet.yaml
index ba54f6894..620dbfbac 100644
--- a/kamelets/fhir-source.kamelet.yaml
+++ b/kamelets/fhir-source.kamelet.yaml
@@ -37,11 +37,9 @@ spec:
 
       Output: the body is a FHIR Bundle of type `searchset`, as JSON text, 
with the number of resources found (`total`) and the resources themselves under 
`entry`. The `Content-Type` header is `application/fhir+json`.
 
-      Good to know: a new search starts about every half second, and every 
search returns all the matching resources again, not only the new ones; add a 
filter such as `_lastUpdated` to `url` to narrow it. `username` and `password` 
are required, even for a server without login.
+      Good to know: a new search starts about every half second unless `delay` 
is set, and every search returns all the matching resources again, not only the 
new ones; add a filter such as `_lastUpdated` to `url` to narrow it. Log in 
with `username` and `password`, or with `accessToken`, or leave them out for a 
server without login; when both kinds are set, both are sent.
     required:
       - serverUrl
-      - username
-      - password
     type: object
     properties:
       serverUrl:
@@ -69,7 +67,7 @@ spec:
         enum: ["DSTU2", "DSTU2_HL7ORG", "DSTU2_1", "DSTU3", "R4", "R5"]
       username:
         title: Username
-        description: The user to log in to the server as, with Basic 
authentication.
+        description: The user to log in to the server as, with Basic 
authentication. Leave it out for a server without login.
         type: string
         x-descriptors:
         - urn:camel:group:credentials
@@ -80,6 +78,41 @@ spec:
         format: password
         x-descriptors:
         - urn:camel:group:credentials
+      delay:
+        title: Delay
+        description: How long to wait after a search before the next one 
starts, in milliseconds. For example, 60000 is one minute. When it is not set, 
it is 500 (half a second).
+        type: integer
+        example: 60000
+      accessToken:
+        title: Access Token
+        description: An OAuth access token, sent as a Bearer token, for a 
server that uses OAuth, such as SMART on FHIR. Use it instead of `username` and 
`password`.
+        type: string
+        format: password
+        x-descriptors:
+        - urn:camel:group:credentials
+      proxyHost:
+        title: Proxy Host
+        description: The host name of an HTTP proxy to reach the server 
through. Use it with `proxyPort`.
+        type: string
+        example: proxy.example.com
+      proxyPort:
+        title: Proxy Port
+        description: The port of the HTTP proxy in `proxyHost`.
+        type: integer
+        example: 3128
+      proxyUser:
+        title: Proxy User
+        description: The user to log in to the HTTP proxy as, when the proxy 
needs a login.
+        type: string
+        x-descriptors:
+        - urn:camel:group:credentials
+      proxyPassword:
+        title: Proxy Password
+        description: The password of `proxyUser` for the HTTP proxy.
+        type: string
+        format: password
+        x-descriptors:
+        - urn:camel:group:credentials
       prettyPrint:
         title: Json Pretty Print
         description: If true, the JSON in the body is indented over several 
lines; if false, it is on one line.
@@ -93,7 +126,7 @@ spec:
     - "camel:kamelet"
   template:
     from:
-      uri: 
"fhir://search/searchByUrl?encoding={{encoding}}&fhirVersion={{fhirVersion}}&password=RAW({{password}})&prettyPrint={{prettyPrint}}&serverUrl={{serverUrl}}&url={{url}}&username=RAW({{username}})"
+      uri: 
"fhir://search/searchByUrl?accessToken=RAW({{?accessToken}})&delay={{?delay}}&encoding={{encoding}}&fhirVersion={{fhirVersion}}&password=RAW({{?password}})&prettyPrint={{prettyPrint}}&proxyHost={{?proxyHost}}&proxyPassword=RAW({{?proxyPassword}})&proxyPort={{?proxyPort}}&proxyUser=RAW({{?proxyUser}})&serverUrl={{serverUrl}}&url={{url}}&username=RAW({{?username}})"
       steps:
         - marshal:
             fhirJson:
diff --git a/kamelets/ogcapi-features-action.kamelet.yaml 
b/kamelets/ogcapi-features-action.kamelet.yaml
index 7a22f118a..d57dd1323 100644
--- a/kamelets/ogcapi-features-action.kamelet.yaml
+++ b/kamelets/ogcapi-features-action.kamelet.yaml
@@ -39,7 +39,7 @@ spec:
 
       Output: the body is a GeoJSON feature collection, as JSON text, with at 
most `limit` features. The headers of the HTTP response, such as 
`Content-Type`, are set as headers.
 
-      Good to know: `split` does not change what the next step receives: it 
still gets the whole collection, once per message. An HTTP error from the 
server, such as an unknown collection, fails the message.
+      Good to know: `split` does not change what the next step receives: it 
still gets the whole collection, once per message. An HTTP error from the 
server, such as an unknown collection, fails the message. A service that cannot 
be reached within `connectTimeout`, or does not answer within 
`responseTimeout`, fails the message; when they are not set, it waits up to 3 
minutes.
     required:
       - url
       - collection
@@ -78,6 +78,16 @@ spec:
         example: "property1=1&property2=dos"
         default: ""
         type: string
+      connectTimeout:
+        title: Connect Timeout
+        description: How long to wait for the connection to the service to be 
set up, in milliseconds. When it is not set, it waits up to 3 minutes, or less 
when the operating system gives up first. A service that cannot be reached in 
time fails the message.
+        type: integer
+        example: 5000
+      responseTimeout:
+        title: Response Timeout
+        description: How long to wait for the answer of the service once the 
request is sent, in milliseconds. When it is not set, it is 180000 (3 minutes). 
A service that does not answer in time fails the message.
+        type: integer
+        example: 30000
   types:
     in:
       mediaType: text/plain
@@ -107,6 +117,9 @@ spec:
               simple: {}
         - to:
             uri: "{{url}}/collections/{{collection}}/items"
+            parameters:
+              connectTimeout: "{{?connectTimeout}}"
+              responseTimeout: "{{?responseTimeout}}"
         - removeHeader:
             name: Accept
         - removeHeader:
diff --git a/kamelets/snmp-source.kamelet.yaml 
b/kamelets/snmp-source.kamelet.yaml
index ab2989db1..8327a0718 100644
--- a/kamelets/snmp-source.kamelet.yaml
+++ b/kamelets/snmp-source.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
 
       Output: the body is XML text with one `entry` per value, each with its 
`oid` (the identifier of the value, such as `1.3.6.1.2.1.1.3.0` for the uptime) 
and its `value`, inside an `snmp` element. For a trap, the `peerAddress` header 
is the address of the device that sent it.
 
-      Good to know: with `type` set to `TRAP`, `host` and `port` are the 
address to listen on, not a device; traps are usually sent to port 162, but 
`port` is 161 by default, and a port below 1024 needs administrator rights on 
most systems. A device that does not answer a poll gives no message. SNMP v1 
and v2c send the community string in clear text; prefer v3 when the device 
supports it.
+      Good to know: with `type` set to `TRAP`, `host` and `port` are the 
address to listen on, not a device; traps are usually sent to port 162, but 
`port` is 161 by default, and a port below 1024 needs administrator rights on 
most systems. A device that does not answer a poll gives no message: it is sent 
again `retries` times, each time after waiting `snmpTimeout` for the answer; 
when they are not set, that is 2 more times, after 1.5 seconds each. SNMP v1 
and v2c send the community stri [...]
     required:
     - host
     type: object
@@ -74,6 +74,27 @@ spec:
         description: How long to wait between two polls, in milliseconds. For 
example, 60000 is one minute. Not used for `TRAP`.
         type: integer
         default: 60000
+      initialDelay:
+        title: Initial Delay
+        description: How long to wait before the first poll, in milliseconds. 
When it is not set, it is 1000 (one second). Not used for `TRAP`.
+        type: integer
+        example: 10000
+      snmpTimeout:
+        title: SNMP Timeout
+        description: How long to wait for the answer of the device to a poll, 
in milliseconds, before the poll is sent again or given up. When it is not set, 
it is 1500. Not used for `TRAP`.
+        type: integer
+        example: 5000
+      retries:
+        title: Retries
+        description: How many times a poll is sent again when the device does 
not answer within `snmpTimeout`. When it is not set, it is 2. Not used for 
`TRAP`.
+        type: integer
+        example: 0
+      snmpContextName:
+        title: SNMP Context Name
+        description: The SNMP v3 context to read the values from, for a device 
that serves several sets of values (contexts) under one address, such as one 
per virtual router. When it is not set, the default context of the device is 
read. Only used with `snmpVersion` 3, and not used for `TRAP`.
+        type: string
+        example: vrf-blue
+        pattern: "^[^\\s]+$"
       snmpVersion:
         title: SNMP Version
         description: The version of SNMP to use. 0 is v1, 1 is v2c and 3 is 
v3. It must match the version the device or the trap sender uses.
@@ -146,6 +167,10 @@ spec:
       parameters:
         host: "{{host}}"
         port: "{{port}}"
+        initialDelay: "{{?initialDelay}}"
+        retries: "{{?retries}}"
+        snmpContextName: "RAW({{?snmpContextName}})"
+        timeout: "{{?snmpTimeout}}"
         authenticationPassphrase: "RAW({{?authenticationPassphrase}})"
         authenticationProtocol: "{{?authenticationProtocol}}"
         delay: "{{delay}}"
diff --git a/kamelets/splunk-hec-sink.kamelet.yaml 
b/kamelets/splunk-hec-sink.kamelet.yaml
index 1ff4bc47a..65d4a343e 100644
--- a/kamelets/splunk-hec-sink.kamelet.yaml
+++ b/kamelets/splunk-hec-sink.kamelet.yaml
@@ -39,7 +39,7 @@ spec:
 
       Output: the message is unchanged.
 
-      Good to know: when `index`, `source` and `sourceType` are not set, the 
events go to the index `camel` with the source and source type `camel`, so set 
them for your Splunk. The `host` field of the event is the IP address of the 
machine that runs the integration, unless `hostPayload` is set. It connects 
with HTTPS and checks the certificate of the server, unless `https` or 
`skipTlsVerify` say otherwise.
+      Good to know: when `index`, `source` and `sourceType` are not set, the 
events go to the index `camel` with the source and source type `camel`, so set 
them for your Splunk. The `host` field of the event is the IP address of the 
machine that runs the integration, unless `hostPayload` is set. It connects 
with HTTPS and checks the certificate of the server, unless `https` or 
`skipTlsVerify` say otherwise. It sends to the event endpoint 
`/services/collector/event`; with `splunkEndpoint` [...]
     required:
       - splunkUrl
       - token
@@ -57,6 +57,12 @@ spec:
         format: password
         x-descriptors:
         - urn:camel:group:credentials
+      splunkEndpoint:
+        title: Splunk Endpoint
+        description: The path of the HTTP Event Collector endpoint to send to, 
starting with `/`, optionally followed by query parameters. When it is not set, 
it is `/services/collector/event`. With `/services/collector/raw`, Splunk 
stores the whole JSON object that the Kamelet sends as the text of the event, 
and takes the index, source and source type from the token and from query 
parameters, not from `index`, `source` and `sourceType`, such as 
`/services/collector/raw?index=main&source [...]
+        type: string
+        example: /services/collector/raw
+        pattern: "^/[^\\s]*$"
       hostPayload:
         title: Host of the Event
         description: The value of the `host` field of every event, such as the 
name of the machine or application that the events are about. It is not the 
address of Splunk. When it is not set, the IP address of the machine that runs 
the integration is used.
@@ -116,6 +122,7 @@ spec:
             uri: splunk-hec
             parameters:
               splunkURL: "{{splunkUrl}}"
+              splunkEndpoint: "RAW({{?splunkEndpoint}})"
               bodyOnly: "{{?bodyOnly}}"
               headersOnly: "{{?headersOnly}}"
               host: "{{?hostPayload}}"
diff --git 
a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json 
b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
index da35be305..64ec3ca0a 100644
--- a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
+++ b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
@@ -745,7 +745,7 @@
     "supportLevel" : "Stable",
     "title" : "FHIR Sink",
     "summary" : "Sends each message, a FHIR resource such as a Patient or an 
Observation, to a FHIR server of healthcare data, to create, update, delete or 
validate it there.",
-    "description" : "Sends each message, a FHIR resource such as a Patient or 
an Observation, to a FHIR server of healthcare data, to create, update, delete 
or validate it there.\n\nUse it to write healthcare records into a FHIR server, 
for example to create a Patient for each new admission, or to update an 
Observation that a device measured. To read resources from a FHIR server, use 
`fhir-source`.\n\nInput: the body is the FHIR resource, as JSON text, or as XML 
text with `encoding` set  [...]
+    "description" : "Sends each message, a FHIR resource such as a Patient or 
an Observation, to a FHIR server of healthcare data, to create, update, delete 
or validate it there.\n\nUse it to write healthcare records into a FHIR server, 
for example to create a Patient for each new admission, or to update an 
Observation that a device measured. To read resources from a FHIR server, use 
`fhir-source`.\n\nInput: the body is the FHIR resource, as JSON text, or as XML 
text with `encoding` set  [...]
     "group" : "FHIR",
     "namespace" : "API",
     "provider" : "Apache Software Foundation"
@@ -755,7 +755,7 @@
     "supportLevel" : "Stable",
     "title" : "FHIR Source",
     "summary" : "Runs the same search on a FHIR server of healthcare data over 
and over, by default for all the Patient resources, and sends each search 
result, a FHIR Bundle, as one message.",
-    "description" : "Runs the same search on a FHIR server of healthcare data 
over and over, by default for all the Patient resources, and sends each search 
result, a FHIR Bundle, as one message.\n\nUse it to copy healthcare records, 
such as patients or observations, from a FHIR server into another system, or to 
check a FHIR server on a schedule. To create or update resources on a FHIR 
server, use `fhir-sink`.\n\nOutput: the body is a FHIR Bundle of type 
`searchset`, as JSON text, with t [...]
+    "description" : "Runs the same search on a FHIR server of healthcare data 
over and over, by default for all the Patient resources, and sends each search 
result, a FHIR Bundle, as one message.\n\nUse it to copy healthcare records, 
such as patients or observations, from a FHIR server into another system, or to 
check a FHIR server on a schedule. To create or update resources on a FHIR 
server, use `fhir-sink`.\n\nOutput: the body is a FHIR Bundle of type 
`searchset`, as JSON text, with t [...]
     "group" : "FHIR",
     "namespace" : "API",
     "provider" : "Apache Software Foundation"
@@ -1695,7 +1695,7 @@
     "supportLevel" : "Stable",
     "title" : "OGC Api Feature Get Item Action",
     "summary" : "Fetches the features of one collection, such as the lakes or 
the buildings of an area, from a server that implements the OGC API Features 
standard, and gives them as GeoJSON.",
-    "description" : "Fetches the features of one collection, such as the lakes 
or the buildings of an area, from a server that implements the OGC API Features 
standard, and gives them as GeoJSON.\n\nUse it to bring map data from a 
geographic data service into a flow, for example to load the features of an 
area into a database or to check them against a list of places.\n\nInput: the 
body, when it is not empty, is added to the query of the request, as text such 
as `name=Lake Baikal`, so ea [...]
+    "description" : "Fetches the features of one collection, such as the lakes 
or the buildings of an area, from a server that implements the OGC API Features 
standard, and gives them as GeoJSON.\n\nUse it to bring map data from a 
geographic data service into a flow, for example to load the features of an 
area into a database or to check them against a list of places.\n\nInput: the 
body, when it is not empty, is added to the query of the request, as text such 
as `name=Lake Baikal`, so ea [...]
     "group" : "Geospatial",
     "namespace" : "Geo",
     "provider" : "Apache Software Foundation"
@@ -2055,7 +2055,7 @@
     "supportLevel" : "Preview",
     "title" : "SNMP Source",
     "summary" : "Reads values, such as uptime or interface counters, from a 
network device over SNMP at a regular interval, or receives the SNMP traps that 
devices send, one message per reading or trap.",
-    "description" : "Reads values, such as uptime or interface counters, from 
a network device over SNMP at a regular interval, or receives the SNMP traps 
that devices send, one message per reading or trap.\n\nUse it to monitor 
routers, switches, printers or servers that speak SNMP, for example to store 
their counters over time, or to forward their alarms (traps) to a ticketing or 
chat system.\n\nOutput: the body is XML text with one `entry` per value, each 
with its `oid` (the identifier [...]
+    "description" : "Reads values, such as uptime or interface counters, from 
a network device over SNMP at a regular interval, or receives the SNMP traps 
that devices send, one message per reading or trap.\n\nUse it to monitor 
routers, switches, printers or servers that speak SNMP, for example to store 
their counters over time, or to forward their alarms (traps) to a ticketing or 
chat system.\n\nOutput: the body is XML text with one `entry` per value, each 
with its `oid` (the identifier [...]
     "group" : "SNMP",
     "namespace" : "Monitoring",
     "provider" : "Apache Software Foundation"
@@ -2105,7 +2105,7 @@
     "supportLevel" : "Stable",
     "title" : "Splunk HEC Sink",
     "summary" : "Sends each message as an event to Splunk through its HTTP 
Event Collector (HEC), for searching, dashboards and alerts in Splunk.",
-    "description" : "Sends each message as an event to Splunk through its HTTP 
Event Collector (HEC), for searching, dashboards and alerts in Splunk.\n\nUse 
it to send application logs, audit records, metrics or business events from any 
flow into a Splunk index.\n\nInput: the body is the event, as text or as 
structured data such as a Map, which is sent as a JSON object. By default the 
event sent to Splunk is a JSON object with the headers of the message under 
`headers` and the body under [...]
+    "description" : "Sends each message as an event to Splunk through its HTTP 
Event Collector (HEC), for searching, dashboards and alerts in Splunk.\n\nUse 
it to send application logs, audit records, metrics or business events from any 
flow into a Splunk index.\n\nInput: the body is the event, as text or as 
structured data such as a Map, which is sent as a JSON object. By default the 
event sent to Splunk is a JSON object with the headers of the message under 
`headers` and the body under [...]
     "group" : "SPLUNK",
     "namespace" : "Monitoring",
     "provider" : "Apache Software Foundation"
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/fhir-sink.kamelet.yaml 
b/library/camel-kamelets/src/main/resources/kamelets/fhir-sink.kamelet.yaml
index 33fabbde1..a64154848 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/fhir-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/fhir-sink.kamelet.yaml
@@ -40,7 +40,7 @@ spec:
 
       Output: when it is used inside a route, the body afterwards is the 
outcome of the operation, as a Java object of the HAPI FHIR library, with the 
id of the resource; it is not JSON.
 
-      Good to know: a body that is not a valid FHIR resource of the chosen 
`fhirVersion` fails the message. Operations that do not take a resource, such 
as `READ` or `SEARCH`, fail.
+      Good to know: a body that is not a valid FHIR resource of the chosen 
`fhirVersion` fails the message. Operations that do not take a resource, such 
as `READ` or `SEARCH`, fail. Before the first message, it reads the capability 
statement of the server at `/metadata`, unless `validationMode` is `NEVER`. A 
server that does not answer within `connectionTimeout` and `socketTimeout`, 10 
seconds each when they are not set, fails the message.
     required:
     - serverUrl
     - apiName
@@ -89,6 +89,31 @@ spec:
         description: "If true, the connection to the server is set up at the 
first message instead of when the integration starts, so that the integration 
can start while the server is not reachable. The first message then takes a 
little longer."
         type: boolean
         default: false
+      connectionTimeout:
+        title: Connection Timeout
+        description: How long to wait for the connection to the server to be 
set up, in milliseconds. When it is not set, it is 10000 (10 seconds). A server 
that cannot be reached in time fails the message.
+        type: integer
+        example: 5000
+      socketTimeout:
+        title: Socket Timeout
+        description: How long to wait for the answer of the server to a 
request, in milliseconds. When it is not set, it is 10000 (10 seconds). A 
server that does not answer in time fails the message, so raise it for a slow 
server.
+        type: integer
+        example: 60000
+      compress:
+        title: Compress
+        description: If true, the resource sent to the server is compressed 
with GZIP, with the header `Content-Encoding` set to `gzip`, which saves 
bandwidth for large resources. The server must accept GZIP requests.
+        type: boolean
+        example: true
+      summary:
+        title: Summary
+        description: Asks the server to answer with a short form of the 
resource, with the FHIR `_summary` parameter on every request, such as `TRUE` 
for the summary elements only, or `DATA` for all but the text. The server still 
stores the whole resource; only the answer, the body afterwards, is shorter. 
When it is not set, the server answers in full.
+        type: string
+        enum: ["COUNT", "TEXT", "DATA", "TRUE", "FALSE"]
+      validationMode:
+        title: Validation Mode
+        description: Whether the capability statement of the server, at 
`/metadata`, is read before the first message. With `ONCE`, a server that does 
not answer it fails the message; `NEVER` does not read it, for a server without 
`/metadata`. When it is not set, it is `ONCE`.
+        type: string
+        enum: ["NEVER", "ONCE"]
       proxyHost:
         title: Proxy Host
         description: The host name of an HTTP proxy to reach the server 
through. Use it with `proxyPort`.
@@ -159,4 +184,4 @@ spec:
                         prettyPrint: "{{prettyPrint}}"
                         fhirVersion: "{{fhirVersion}}"
         - to:
-            uri: 
"fhir://{{apiName}}/{{methodName}}?accessToken=RAW({{?accessToken}})&encoding={{encoding}}&fhirVersion={{fhirVersion}}&inBody=resource&lazyStartProducer={{lazyStart}}&log={{log}}&password=RAW({{?password}})&prettyPrint={{prettyPrint}}&proxyHost={{?proxyHost}}&proxyPassword=RAW({{?proxyPassword}})&proxyPort={{?proxyPort}}&proxyUser=RAW({{?proxyUser}})&serverUrl={{serverUrl}}&username=RAW({{?username}})"
+            uri: 
"fhir://{{apiName}}/{{methodName}}?accessToken=RAW({{?accessToken}})&compress={{?compress}}&connectionTimeout={{?connectionTimeout}}&encoding={{encoding}}&fhirVersion={{fhirVersion}}&inBody=resource&lazyStartProducer={{lazyStart}}&log={{log}}&password=RAW({{?password}})&prettyPrint={{prettyPrint}}&proxyHost={{?proxyHost}}&proxyPassword=RAW({{?proxyPassword}})&proxyPort={{?proxyPort}}&proxyUser=RAW({{?proxyUser}})&serverUrl={{serverUrl}}&socketTimeout={{?socketTimeout}}&s
 [...]
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/fhir-source.kamelet.yaml 
b/library/camel-kamelets/src/main/resources/kamelets/fhir-source.kamelet.yaml
index ba54f6894..620dbfbac 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/fhir-source.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/fhir-source.kamelet.yaml
@@ -37,11 +37,9 @@ spec:
 
       Output: the body is a FHIR Bundle of type `searchset`, as JSON text, 
with the number of resources found (`total`) and the resources themselves under 
`entry`. The `Content-Type` header is `application/fhir+json`.
 
-      Good to know: a new search starts about every half second, and every 
search returns all the matching resources again, not only the new ones; add a 
filter such as `_lastUpdated` to `url` to narrow it. `username` and `password` 
are required, even for a server without login.
+      Good to know: a new search starts about every half second unless `delay` 
is set, and every search returns all the matching resources again, not only the 
new ones; add a filter such as `_lastUpdated` to `url` to narrow it. Log in 
with `username` and `password`, or with `accessToken`, or leave them out for a 
server without login; when both kinds are set, both are sent.
     required:
       - serverUrl
-      - username
-      - password
     type: object
     properties:
       serverUrl:
@@ -69,7 +67,7 @@ spec:
         enum: ["DSTU2", "DSTU2_HL7ORG", "DSTU2_1", "DSTU3", "R4", "R5"]
       username:
         title: Username
-        description: The user to log in to the server as, with Basic 
authentication.
+        description: The user to log in to the server as, with Basic 
authentication. Leave it out for a server without login.
         type: string
         x-descriptors:
         - urn:camel:group:credentials
@@ -80,6 +78,41 @@ spec:
         format: password
         x-descriptors:
         - urn:camel:group:credentials
+      delay:
+        title: Delay
+        description: How long to wait after a search before the next one 
starts, in milliseconds. For example, 60000 is one minute. When it is not set, 
it is 500 (half a second).
+        type: integer
+        example: 60000
+      accessToken:
+        title: Access Token
+        description: An OAuth access token, sent as a Bearer token, for a 
server that uses OAuth, such as SMART on FHIR. Use it instead of `username` and 
`password`.
+        type: string
+        format: password
+        x-descriptors:
+        - urn:camel:group:credentials
+      proxyHost:
+        title: Proxy Host
+        description: The host name of an HTTP proxy to reach the server 
through. Use it with `proxyPort`.
+        type: string
+        example: proxy.example.com
+      proxyPort:
+        title: Proxy Port
+        description: The port of the HTTP proxy in `proxyHost`.
+        type: integer
+        example: 3128
+      proxyUser:
+        title: Proxy User
+        description: The user to log in to the HTTP proxy as, when the proxy 
needs a login.
+        type: string
+        x-descriptors:
+        - urn:camel:group:credentials
+      proxyPassword:
+        title: Proxy Password
+        description: The password of `proxyUser` for the HTTP proxy.
+        type: string
+        format: password
+        x-descriptors:
+        - urn:camel:group:credentials
       prettyPrint:
         title: Json Pretty Print
         description: If true, the JSON in the body is indented over several 
lines; if false, it is on one line.
@@ -93,7 +126,7 @@ spec:
     - "camel:kamelet"
   template:
     from:
-      uri: 
"fhir://search/searchByUrl?encoding={{encoding}}&fhirVersion={{fhirVersion}}&password=RAW({{password}})&prettyPrint={{prettyPrint}}&serverUrl={{serverUrl}}&url={{url}}&username=RAW({{username}})"
+      uri: 
"fhir://search/searchByUrl?accessToken=RAW({{?accessToken}})&delay={{?delay}}&encoding={{encoding}}&fhirVersion={{fhirVersion}}&password=RAW({{?password}})&prettyPrint={{prettyPrint}}&proxyHost={{?proxyHost}}&proxyPassword=RAW({{?proxyPassword}})&proxyPort={{?proxyPort}}&proxyUser=RAW({{?proxyUser}})&serverUrl={{serverUrl}}&url={{url}}&username=RAW({{?username}})"
       steps:
         - marshal:
             fhirJson:
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/ogcapi-features-action.kamelet.yaml
 
b/library/camel-kamelets/src/main/resources/kamelets/ogcapi-features-action.kamelet.yaml
index 7a22f118a..d57dd1323 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/ogcapi-features-action.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/ogcapi-features-action.kamelet.yaml
@@ -39,7 +39,7 @@ spec:
 
       Output: the body is a GeoJSON feature collection, as JSON text, with at 
most `limit` features. The headers of the HTTP response, such as 
`Content-Type`, are set as headers.
 
-      Good to know: `split` does not change what the next step receives: it 
still gets the whole collection, once per message. An HTTP error from the 
server, such as an unknown collection, fails the message.
+      Good to know: `split` does not change what the next step receives: it 
still gets the whole collection, once per message. An HTTP error from the 
server, such as an unknown collection, fails the message. A service that cannot 
be reached within `connectTimeout`, or does not answer within 
`responseTimeout`, fails the message; when they are not set, it waits up to 3 
minutes.
     required:
       - url
       - collection
@@ -78,6 +78,16 @@ spec:
         example: "property1=1&property2=dos"
         default: ""
         type: string
+      connectTimeout:
+        title: Connect Timeout
+        description: How long to wait for the connection to the service to be 
set up, in milliseconds. When it is not set, it waits up to 3 minutes, or less 
when the operating system gives up first. A service that cannot be reached in 
time fails the message.
+        type: integer
+        example: 5000
+      responseTimeout:
+        title: Response Timeout
+        description: How long to wait for the answer of the service once the 
request is sent, in milliseconds. When it is not set, it is 180000 (3 minutes). 
A service that does not answer in time fails the message.
+        type: integer
+        example: 30000
   types:
     in:
       mediaType: text/plain
@@ -107,6 +117,9 @@ spec:
               simple: {}
         - to:
             uri: "{{url}}/collections/{{collection}}/items"
+            parameters:
+              connectTimeout: "{{?connectTimeout}}"
+              responseTimeout: "{{?responseTimeout}}"
         - removeHeader:
             name: Accept
         - removeHeader:
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/snmp-source.kamelet.yaml 
b/library/camel-kamelets/src/main/resources/kamelets/snmp-source.kamelet.yaml
index ab2989db1..8327a0718 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/snmp-source.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/snmp-source.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
 
       Output: the body is XML text with one `entry` per value, each with its 
`oid` (the identifier of the value, such as `1.3.6.1.2.1.1.3.0` for the uptime) 
and its `value`, inside an `snmp` element. For a trap, the `peerAddress` header 
is the address of the device that sent it.
 
-      Good to know: with `type` set to `TRAP`, `host` and `port` are the 
address to listen on, not a device; traps are usually sent to port 162, but 
`port` is 161 by default, and a port below 1024 needs administrator rights on 
most systems. A device that does not answer a poll gives no message. SNMP v1 
and v2c send the community string in clear text; prefer v3 when the device 
supports it.
+      Good to know: with `type` set to `TRAP`, `host` and `port` are the 
address to listen on, not a device; traps are usually sent to port 162, but 
`port` is 161 by default, and a port below 1024 needs administrator rights on 
most systems. A device that does not answer a poll gives no message: it is sent 
again `retries` times, each time after waiting `snmpTimeout` for the answer; 
when they are not set, that is 2 more times, after 1.5 seconds each. SNMP v1 
and v2c send the community stri [...]
     required:
     - host
     type: object
@@ -74,6 +74,27 @@ spec:
         description: How long to wait between two polls, in milliseconds. For 
example, 60000 is one minute. Not used for `TRAP`.
         type: integer
         default: 60000
+      initialDelay:
+        title: Initial Delay
+        description: How long to wait before the first poll, in milliseconds. 
When it is not set, it is 1000 (one second). Not used for `TRAP`.
+        type: integer
+        example: 10000
+      snmpTimeout:
+        title: SNMP Timeout
+        description: How long to wait for the answer of the device to a poll, 
in milliseconds, before the poll is sent again or given up. When it is not set, 
it is 1500. Not used for `TRAP`.
+        type: integer
+        example: 5000
+      retries:
+        title: Retries
+        description: How many times a poll is sent again when the device does 
not answer within `snmpTimeout`. When it is not set, it is 2. Not used for 
`TRAP`.
+        type: integer
+        example: 0
+      snmpContextName:
+        title: SNMP Context Name
+        description: The SNMP v3 context to read the values from, for a device 
that serves several sets of values (contexts) under one address, such as one 
per virtual router. When it is not set, the default context of the device is 
read. Only used with `snmpVersion` 3, and not used for `TRAP`.
+        type: string
+        example: vrf-blue
+        pattern: "^[^\\s]+$"
       snmpVersion:
         title: SNMP Version
         description: The version of SNMP to use. 0 is v1, 1 is v2c and 3 is 
v3. It must match the version the device or the trap sender uses.
@@ -146,6 +167,10 @@ spec:
       parameters:
         host: "{{host}}"
         port: "{{port}}"
+        initialDelay: "{{?initialDelay}}"
+        retries: "{{?retries}}"
+        snmpContextName: "RAW({{?snmpContextName}})"
+        timeout: "{{?snmpTimeout}}"
         authenticationPassphrase: "RAW({{?authenticationPassphrase}})"
         authenticationProtocol: "{{?authenticationProtocol}}"
         delay: "{{delay}}"
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/splunk-hec-sink.kamelet.yaml
 
b/library/camel-kamelets/src/main/resources/kamelets/splunk-hec-sink.kamelet.yaml
index 1ff4bc47a..65d4a343e 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/splunk-hec-sink.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/splunk-hec-sink.kamelet.yaml
@@ -39,7 +39,7 @@ spec:
 
       Output: the message is unchanged.
 
-      Good to know: when `index`, `source` and `sourceType` are not set, the 
events go to the index `camel` with the source and source type `camel`, so set 
them for your Splunk. The `host` field of the event is the IP address of the 
machine that runs the integration, unless `hostPayload` is set. It connects 
with HTTPS and checks the certificate of the server, unless `https` or 
`skipTlsVerify` say otherwise.
+      Good to know: when `index`, `source` and `sourceType` are not set, the 
events go to the index `camel` with the source and source type `camel`, so set 
them for your Splunk. The `host` field of the event is the IP address of the 
machine that runs the integration, unless `hostPayload` is set. It connects 
with HTTPS and checks the certificate of the server, unless `https` or 
`skipTlsVerify` say otherwise. It sends to the event endpoint 
`/services/collector/event`; with `splunkEndpoint` [...]
     required:
       - splunkUrl
       - token
@@ -57,6 +57,12 @@ spec:
         format: password
         x-descriptors:
         - urn:camel:group:credentials
+      splunkEndpoint:
+        title: Splunk Endpoint
+        description: The path of the HTTP Event Collector endpoint to send to, 
starting with `/`, optionally followed by query parameters. When it is not set, 
it is `/services/collector/event`. With `/services/collector/raw`, Splunk 
stores the whole JSON object that the Kamelet sends as the text of the event, 
and takes the index, source and source type from the token and from query 
parameters, not from `index`, `source` and `sourceType`, such as 
`/services/collector/raw?index=main&source [...]
+        type: string
+        example: /services/collector/raw
+        pattern: "^/[^\\s]*$"
       hostPayload:
         title: Host of the Event
         description: The value of the `host` field of every event, such as the 
name of the machine or application that the events are about. It is not the 
address of Splunk. When it is not set, the IP address of the machine that runs 
the integration is used.
@@ -116,6 +122,7 @@ spec:
             uri: splunk-hec
             parameters:
               splunkURL: "{{splunkUrl}}"
+              splunkEndpoint: "RAW({{?splunkEndpoint}})"
               bodyOnly: "{{?bodyOnly}}"
               headersOnly: "{{?headersOnly}}"
               host: "{{?hostPayload}}"

Reply via email to