Getting Data In

JSON files are not being onboarded intermittently via SQS based S3 input?

soumdey0192
Explorer

Hello All,

We have issue wherein JSON files are not coming in intermittently into Splunk from a SQS based S3 input.

The JSON file id generated everyday at 3 AM which is generally ingested into Splunk except for times when eventhough the file gets generated, but the file is not ingested on Splunk.

Unfortunately, there is no logs whatsoever generated on Splunk internal logs for times when the file is not ingested into Splunk.

Can anyone suggest what can be the issue here or if this has been encountered by someone?

The version of aws add-on being used here is, 5.0.4 and the Splunk version is 8.1.5.

Labels (2)
Tags (3)
0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...