Send data from Edge Processors to the Splunk Cloud Platform deployment connected to your tenant

As part of the first-time setup process for the Edge Processor solution, you created a connection between your cloud tenant and your Splunk Cloud Platform deployment. You can use this connection to send data from Edge Processors to the connected Splunk Cloud Platform deployment. To do this, you must create a pipeline that uses a destination that is associated with this connection, and then apply the pipeline to an Edge Processor. If you want to send data to an index that was created after the Splunk Cloud Platform deployment was connected to the tenant, then you might need to refresh the connection before that index becomes available as a destination.

The specific index that the data from an Edge Processor gets routed to is determined by a precedence order of configurations. For more information, see Index precedence order when using S2S.

You can also send data from an Edge Processor to a Splunk platform deployment that is not connected to your tenant. For more information, see Sending data from Edge Processors to Splunk Cloud Platform or Splunk Enterprise.

Prerequisites

Make sure that your Splunk Cloud Platform deployment is connected to your cloud tenant, and that the indexers and indexes from that deployment are available to your tenant.

To verify if this connection has been configured correctly, navigate to the Destinations page and select the Splunk tab. Then, confirm the following:

• Indexers from your Splunk Cloud Platform deployment are available as Splunk platform S2S destinations that have the Tenant paired property. To verify whether a destination has this property, select the destination to open a side panel with configuration details, and then check if the Kind field in the panel includes the Tenant paired tag.
• Indexes from your Splunk Cloud Platform deployment are available to the tenant. To verify this, first select the Splunk platform S2S destination corresponding to your deployment. Then, in the side panel that contains destination details, select View indexes.

If you do not see any destinations that have these characteristics, make sure that you have completed the setup process described in First-time setup instructions for the Edge Processor solution.

If an index that you expect to see is not appearing on the View indexes list, confirm that the index is configured to be available to the tenant and then refresh the connection between the tenant and the Splunk Cloud Platform deployment. For detailed instructions, see the Make more indexes available to the tenant section that follows.

Make more indexes available to the tenant

If any indexes that you want to send data to are not listed on the View indexes list, then complete the following steps to make those indexes available. Otherwise, skip these steps and proceed to Create a pipeline that sends data to the connected Splunk Cloud Platform deployment.

1. In your Splunk Cloud Platform deployment, update the role of the service account so that the account can access your indexes:
   1. Log in using your admin credentials.
   2. In the Settings menu, in the Users and authentication section, select Roles.
   3. In the row that lists the role used by your service account, select Edit > Edit.

      The role and service account were created during the initial setup of the Edge Processor solution. See First-time setup instructions for the Edge Processor solution for more information.

   4. On the 3. Indexes tab, select the Included check box for all the indexes that you want to make available.
   5. Select Save.
2. In your cloud tenant, refresh the connection to your Splunk Cloud Platform deployment:
   1. Select the Settings icon () and then select System connections.
   2. On the scpbridge connection, select the Refresh icon ().

The indexes that you added become available on the View indexes list, and you can now send processed data from Edge Processors to these indexes.

Create a pipeline that sends data to the connected Splunk Cloud Platform deployment

1. Navigate to the Pipelines page and then select New pipeline.
2. Select Blank pipeline and then select Next.
3. Specify a subset of the data received by the Edge Processor for this pipeline to process. To do this, you must define a partition by completing these steps:
1. Select the plus icon () next to Partition or select the option that matches how you would like to create your partition in the Suggestions section.
2. Select host, source, or sourcetype in the Field field.
3. Select an operator in the Operator field.
4. Enter the value that your partition should filter by to create the subset in the Value field. Then select Apply. You can create as many conditions for a partition in a pipeline by selecting the plus icon ().
5. Once you have defined your partition, select Next.
4. (Optional) Enter or upload sample data for generating previews that show how your pipeline processes data.

   The sample data must be in the same format as the actual data that you want to process. See Getting sample data for previewing data transformations for more information.

5. Select Next to confirm your sample data or to go to the next step.
6. Select the name of the destination that you want to send data to, and then select Next.
7. (Optional) Specify a target index:
1. In the Index name field, select the name of the index that you want to send your data to.
2. (Optional) In some cases, incoming data already specifies a target index. If you want your Index name selection to override previous target index settings, then select the Overwrite previously specified target index check box.
3. Select Done.

Be aware that the destination index is determined by a precedence order of configurations. See How does an Edge Processor know which index to send data to? for more information.

8. Continue modifying the pipeline to fit your specific use case. You can add processing commands to your pipeline by selecting the plus icon () next to Actions and selecting a data processing action, or by typing SPL2 commands and functions directly in the editor. For instructions on creating pipelines for specific use cases, see the following:
   • Route internal logs from forwarders using an Edge Processor
   • Filter and mask data using an Edge Processor
   • Hash fields using an Edge Processor
   • Route subsets of data using an Edge Processor
   • Enrich data with lookups using an Edge Processor
   • Extract fields from event data using an Edge Processor
   • Extract timestamps from event data using an Edge Processor

When you are done modifying the pipeline, save and apply it to an Edge Processor. If you haven't configured any data sources to send data to the Edge Processor yet, then do so. See the Get data into Edge Processors chapter.