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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Rounding off the Splunk Dashboard Contest

What does a contest-winning Splunk dashboard look like? In this case, it isn't in a browser tab at all. It ...

A Four Part Event Series: AI + Observability: AI Agents, LLMs, Apps, & Infrastructure

AI + Observability: AI Agents, LLMs, Apps, & Infrastructure The rapid evolution of artificial intelligence ...