The Splunk destination plugin syncs data from any CloudQuery source plugin(s) to Splunk
Publisher
cloudquery
Latest version
v2.0.2
Type
Destination
Platforms
Date Published
Loading plugin documentation
We use tracking cookies to understand how you use the product and help us improve it. Please accept cookies to help us improve. You can always opt out later via the link in the footer.
kind: destination
spec:
name: splunk
path: cloudquery/splunk
registry: cloudquery
version: "v2.0.2"
write_mode: "append"
spec:
# Splunk Cloud configuration parameters
host: "${SPLUNK_HOST}"
port: 8088
hec_token: "${SPLUNK_HEC_TOKEN}"
# Optional parameters
# protocol: https
# rest_port: 8089
# session_key: "${SPLUNK_SESSION_KEY}
# index: main
# event_source: cloudquery
# event_sourcetype: _json
# concurrency: 16
# batch_size: 1000
# batch_size_bytes: 5242880
batch_size and batch_size_bytes.append mode only for write_mode.host (string) (optional) (default: "localhost")port (integer) (optional) (default: 8088)hec_token (string) (required)protocol (string) (optional) (default: https)host.rest_port (integer) (optional) (default: 8089)session_key (string) (optional)/services/auth/login Splunk endpointindex (string) (optional) (default: main)event_source (string) (optional) (default: cloudquery)event_sourcetype (string) (optional) (default: _json)batch_size (integer) (optional) (default: 3000)batch_size_bytes (integer) (optional) (default: 15728640 (15 MiB))max_concurrent_requests (integer) (optional) (default: 3)batch_size / max_concurrent_requests around 1000, while keeping max_concurrent_requests as low as possible.
Doing otherwise may result in increasingly high response times from the Splunk instance.insecure_skip_verify_tls (boolean) (optional) (default: false)