DSP 1.2.0 is impacted by the CVE-2021-44228 and CVE-2021-45046 security vulnerabilities from Apache Log4j. To fix these vulnerabilities, you must upgrade to DSP 1.2.4. See Upgrade the Splunk Data Stream Processor to 1.2.4 for upgrade instructions.
On October 30, 2022, all 1.2.x versions of the Splunk Data Stream Processor will reach its end of support date. See the Splunk Software Support Policy for details.
On October 30, 2022, all 1.2.x versions of the Splunk Data Stream Processor will reach its end of support date. See the Splunk Software Support Policy for details.
This documentation does not apply to the most recent version of Splunk® Data Stream Processor.
For documentation on the most recent version, go to the latest release.
Set a default Splunk Enterprise instance for the Send to a Splunk Index (Default for Environment) function
You can set a default Splunk Enterprise or Splunk Cloud Platform instance for the Send to a Splunk Index (Default for Environment) function to send data to.
Best practices are to use the Send to a Splunk Index with Batching function instead.
Steps
- From a node in your deployment cluster, type the following.
./set-config K8S_PIPELINES_DATA_SPLUNKD_HEC_HOST https://<your-splunk-enterprise-hostname> ./set-config K8S_PIPELINES_DATA_SPLUNKD_HEC_PORT 8088 ./set-config K8S_PIPELINES_DATA_SPLUNKD_INDEX main ./set-config K8S_PIPELINES_DATA_SPLUNKD_HEC_TOKEN <HEC token to write to the index>
- After setting the configurations, deploy your changes.
./deploy
Last modified on 17 August, 2021
| Change the admin password | Licensing for the Splunk Data Stream Processor |
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.0, 1.2.1-patch02, 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5, 1.3.0, 1.3.1
Download manual
Feedback submitted, thanks!