Splunk Cloud Platform

Use Ingest Processors

Acrobat logo Download manual as PDF


Acrobat logo Download topic as PDF

Ingest Processor is currently released as a preview only and is not officially supported. See Splunk General Terms for more information. For any questions on this preview, please reach out to ingestprocessor@splunk.com.

Troubleshoot the Ingest Processor solution

Review this page if you are having difficulties with sending data through the Ingest Processor solution. If the problem that you're experiencing is not described on this page, you can find more information by doing the following:

  • Review the list of known issues in the product. See Known issues.

If the problem persists, contact your Splunk representative for assistance. To help expedite the support process, you can generate a diagnostic report and send it to your Splunk representative.

My data is not being processed as expected

When you try to preview a pipeline, the preview results area displays a "No results" message or data that looks incorrect.

Alternatively, when you view the data that was sent from a pipeline to a destination, you notice that the data looks incorrect.

Cause

Reasons why a pipeline might not process data as expected include, but are not limited to, the following:

  • The inbound stream of data is not being broken into events correctly. Data must be pre-processed into distinct events before being processed by a pipeline.
  • The pipeline is not configured correctly.
  • The pipeline preview is for the wrong destination.

Solution

For pipelines with multiple destinations, check to see if you are previewing the correct destination. If not, run the pipeline preview by selecting the Preview Pipeline icon (Image of the Preview Pipeline icon) then select the destination name in the Preview drop-down list.

If this is not the case, make sure that event breaking and merging has been configured correctly for the source type of the data that you want to process.

  1. Navigate to the Source types page.
  2. Look for a source type with a name that matches the value of the sourcetype field in the data that you want to process.
    • If the source type exists, select it to view its configuration details. Confirm that the event breaking and merging behavior is configured correctly for the data that you want to process.
    • If the source type does not exist, then add it to the Ingest Processor service.

If the problem persists after you've verified the source type configuration, then complete the following steps to verify that the processing commands in your pipeline are configured correctly.

  1. If you don't already have your pipeline open for editing, do the following:
    1. Navigate to the Pipelines page.
    2. On the Pipelines page, in the row that lists the pipeline you want to verify, select the Actions icon (Image of the Actions icon) and then select Edit.
  2. From the side panel of the pipeline builder, select Sample data.
  3. Enter or upload sample data that matches the inbound data that you want this pipeline to process, and then select Apply. You can use text strings that represent raw data or CSV values that represent parsed, field-extracted data. See Getting sample data for previewing data transformations for more information.
  4. To generate a preview of what your data looks like after being processed by the pipeline, select the Preview Pipeline icon (This image shows an icon with a triangle pointing right.).
  5. Verify that the preview results match how you want the pipeline to process your data. If the results do not match, or the preview cannot be generated, then make sure that the SPL2 statement of your pipeline is written correctly and contains only supported SPL2 commands. See Ingest Processor pipeline syntax for more information.
Last modified on 15 April, 2024
PREVIOUS
Alerts
 

This documentation applies to the following versions of Splunk Cloud Platform: 9.1.2308 (latest FedRAMP release), 9.1.2312


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