Splunk® Data Stream Processor

Connect to Data Sources and Destinations with DSP

Acrobat logo Download manual as PDF

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.
This documentation does not apply to the most recent version of DSP. Click here for the latest version.
Acrobat logo Download topic as PDF

Create a DSP connection to SignalFx

To send data from a data pipeline in the to a SignalFx endpoint, you must first create a connection using the Connector for SignalFx. You can then use the connection in the Send Metrics Data to SignalFx or Send Trace Data to SignalFx sink functions to send data from your pipeline to your SignalFx endpoint.


Before you can create the SignalFx connection, you must have the following:

  • One of the following types of values for indicating your SignalFx endpoint:
    • A public realm name, which is typically used with cloud-based SignalFx installations that are accessible via publicly available realm names. For example, us1.
    • A URL, which is typically used with non-public SignalFx endpoints. For example, mysignalfx.myhostname.com.
    • A comma-separated list of URLs, which is typically used with the SignalFx API and Ingest endpoints. For example, api.myhostname.com,ingest.myhostname.com.

    IP addresses are not supported.

  • An organization-level access token for authenticating to your SignalFx endpoint. Search for "Work with access tokens" in the SignalFx Infrastructure Monitoring manual for more information about SignalFx access tokens.

If you don't have these credentials, ask your SignalFx administrator for assistance.


  1. In DSP, select the Connections tab and then click Create New Connection.
  2. Select Connector for SignalFx and then click Next.
  3. Complete the following fields:
    Field Description
    Connection Name A unique name for your SignalFx connection.
    Description (Optional) A description of your SignalFx connection
    Endpoint Type The SignalFx endpoint type.
    • Set to public_realm to use a SignalFx public realm as an endpoint.
    • Set to URL to use a hostname as an endpoint.
    • Set to multi_URL to use the SignalFx API and Ingest hostnames as an endpoint.

    This setting is case sensitive. All other values will fail validation.

    Endpoint The SignalFx endpoint.
    • If Endpoint Type is set to public_realm, enter the SignalFx public realm. For example, us1.
    • If Endpoint Type is set to URL, enter the hostname. For example, mysignalfx.myhostname.com. IP addresses are not supported.
    • If Endpoint Type is set to multi_URL, enter the SignalFx API and Ingest hostnames as a comma separated list. For example, api.myhostname.com,ingest.myhostname.com. IP addresses are not supported.
    Org Token Your organization-level SignalFx access token used to authenticate to the SignalFx endpoint.
  4. Any credentials that you upload are transmitted securely by HTTPS, encrypted, and securely stored in a secrets manager.

  5. Click Save.
  6. If you're editing a connection that's being used by an active pipeline, you must reactivate that pipeline after making your changes. When you reactivate a pipeline, you must select where you want to resume data ingestion. See Using activation checkpoints to activate your pipeline in the Use the Data Stream Processor manual for more information.

You can now use your connection in one of the SignalFx sink functions at the end of your data pipeline to send data to SignalFx.

Last modified on 26 February, 2022
Connecting SignalFx to your DSP pipeline
Formatting data into the SignalFx metrics schema

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.0, 1.2.1-patch02

Was this documentation topic helpful?

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