Deployment Architecture

Data Ingestion Only Works After Restart of Splunk

ericpacker
Engager

Scenario:
I am using a script to poll cloud API for data at frequent intervals. The data is stored in archived *.csv.gz files and a UF installed on the same server is configured to monitor the folder:

inputs.conf
[monitor:///apps/splunk/data]
sourcetype = data:1
index = data_1
_TCP_ROUTING = primary_indexers_site_1

The problem is that data only get ingested after a restart of the UF Splunk service on the host, and then almost immediately stops. Meaning I have to restart the UF every time I want to get new/current data.

The script does not appear to be the issue because it is constantly pulling new data into the folder as expected.

Anyone seen this before?

Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...