Splunk® Data Stream Processor

Connect to Data Sources and Destinations with DSP

On April 3, 2023, Splunk Data Stream Processor reached its end of sale, and will reach its end of life on February 28, 2025. If you are an existing DSP customer, please reach out to your account team for more information.

All DSP releases prior to DSP 1.4.0 use Gravity, a Kubernetes orchestrator, which has been announced end-of-life. We have replaced Gravity with an alternative component in DSP 1.4.0. Therefore, we will no longer provide support for versions of DSP prior to DSP 1.4.0 after July 1, 2023. We advise all of our customers to upgrade to DSP 1.4.0 in order to continue to receive full product support from Splunk.
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.

Connecting Amazon CloudWatch to your DSP pipeline

The Amazon CloudWatch connector will be deprecated soon. See the Release Notes for more information.

When creating a data pipeline in Splunk Data Stream Processor, you can connect to Amazon CloudWatch and use it as a data source. Amazon CloudWatch provides system-wide visibility into the resource utilization, application performance, and operational health of your Amazon Web Services (AWS) applications. You can get metrics data from Amazon CloudWatch into a pipeline, transform the data as needed, and then send the transformed data out from the pipeline to a destination of your choosing.

To connect to Amazon CloudWatch as a data source, you must complete the following tasks:

  1. Create a connection that allows DSP to access your Amazon CloudWatch data. See Create a DSP connection to Amazon CloudWatch.
  2. Create a pipeline that starts with the Amazon CloudWatch source function. See the Building a pipeline chapter in the Use the Data Stream Processor manual for instructions on how to build a data pipeline.
  3. Configure the Amazon CloudWatch source function to use your Amazon CloudWatch connection. See Get data from Amazon CloudWatch Metrics in the Function Reference manual.

When you activate the pipeline, the source function starts collecting metrics from Amazon CloudWatch. Each metric event is received into the pipeline as a record.

If your data fails to get into DSP, check the connection settings to make sure you have the correct access key ID and secret access key for your Identity and Access Management (IAM) user. DSP doesn't run a check to see if you enter valid credentials.

How Amazon CloudWatch data is collected

The source function collects data according to the job schedule that you specified in the connection settings. See Scheduled data collection jobs for more information, including a list of the limitations that apply to all scheduled data collection jobs.

The behavior of the Amazon CloudWatch connector might have an impact on the exact timing and scope of your data collection jobs. The first time a scheduled job runs, the connector collects metrics for only one time interval as defined by the Period parameter in the connection settings. For all following scheduled jobs, the connector collects metrics from the last execution up to the current time.

Last modified on 25 March, 2022
Connecting multiple data destinations to your DSP pipeline   Create a DSP connection to Amazon CloudWatch

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5, 1.3.0, 1.3.1

Acrobat logo Download manual
Acrobat logo Download this page

Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters