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!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...