Getting Data In

AWS Add-on 6.3 errors with Generic S3 inputs

steveski
Explorer

We recently updated our AWS Add-on to version 6.3, after which all Generic S3 inputs stopped ingesting. 

Noticed the following error being repeated during every S3 API call.    "parse_csv_with_delimiter'"

The data within our s3 bucket was a tar or .gz extension with either json or xml format,  after the upgrade our previous AWS s3 inputs seemed to have defaulted to csv format.

Ended up recreating several  AWS Generic S3 inputs using a start date from when the Add-on was updated, which allowed the previous missed logs to ingest again.

You can run this search to determine if your system is having a similar issue.

index=_internal level=ERROR ErrorDetail="'parse_csv_with_delimiter'"

 

 

Labels (4)
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!

[Puzzles] Solve, Learn, Repeat: Classic British Rock Bands

This puzzle series (first published here) is based on extracting information from statements about well-known ...

New to the Community? Join Us for an Exclusive Post .conf26 Welcome Session (Plus a ...

Keep the .conf26 Energy Going: Welcome to the Splunk Community! Whether we scanned your badge at the Community ...

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Register to Attend   Join our Tech Talk ...