Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Splunk Observability location.
signalfx_api.png

Splunk Observability

Create a Splunk Observability Destination​

  1. Click the + icon on the Nexset that will be sent to the Splunk Observability destination, and select the Send to Destination option from the menu.

  2. Select the Splunk Observability connector from the list of available destination connectors. Then, select the credential that will be used to connect to your Splunk Observability account, and click Next; or, create a new Splunk Observability credential for use in this flow.

  3. In Nexla, Splunk Observability destinations can be created using pre-built endpoint templates, which expedite destination setup for common Splunk Observability endpoints. Each template is designed specifically for the corresponding Splunk Observability endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Splunk Observability destinations can also be configured manually, allowing you to send data to Splunk Observability endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Splunk Observability endpoints. Each template is designed specifically for the corresponding Splunk Observability endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Send Datapoints

    This endpoint template allows you to send each Nexset record as a data point to Splunk Observability Observability Cloud. Use this template when you need to send metrics or time-series data to Splunk Observability for monitoring and observability.

    • Enter the Ingestion Access Token in the Ingestion Access Token field. This should be the Splunk organization access token that has INGEST permission enabled. The ingestion access token is used to authenticate requests to the Splunk Observability ingestion endpoint and must have INGEST permission enabled.

    This endpoint sends each Nexset record as a data point to Splunk Observability Observability Cloud. The endpoint sends data as JSON in the request body to the Splunk Observability ingestion endpoint. Each record from your Nexset will be sent as a separate data point. The request body should contain the metric data in the format required by the Splunk Observability API, including metric names, values, timestamps, and other metric properties.

    The ingestion access token must have INGEST permission enabled and is used in the X-SF-Token header to authenticate requests to the Splunk Observability ingestion endpoint. The data point structure must match the Splunk Observability API's expected format.

    For detailed information about sending metrics, request body formats, ingestion tokens, and available metric properties, see the Splunk Observability API documentation.

Configure Manually​

Splunk Observability destinations can be manually configured to send data to any valid Splunk Observability API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Splunk Observability API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Splunk Observability API from the Method pulldown menu. Splunk Observability API typically uses POST method for sending data to endpoints.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Splunk Observability API from the Content Format pulldown menu. Splunk Observability API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the Splunk Observability API endpoint to which data will be sent in the URL field. This should be the complete URL to your Splunk Observability endpoint, including your realm (e.g., https://ingest.{realm}.signalfx.com/v2/datapoint). Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The Splunk Observability API endpoint URL should point to the endpoint where you want to send metrics or data points. The endpoint URL should include your realm (from your credential) and the appropriate API path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the Splunk Observability API. The request body should contain the resource data formatted as JSON, with field names matching the Splunk Observability API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the Splunk Observability API's expected format for the specific endpoint you're using. Splunk Observability API uses specific structures for different endpoints (datapoints, events, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the Splunk Observability API documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.