All Apps and Add-ons

Splunk Add-on for Amazon Web Services: Why are fields appearing with Records{} prefix?

chanmic
New Member

Hi All,

I have installed the Splunk Add-on for AWS and I am able to ingest S3 logs into Splunk, but the dashboards are not working. When I look at the fields, I can see a lot of them are appearing with a pre-fix of Records{}. E.g., Records{}.requestID, Records{}.eventType etc...

I believe this is affecting the search. I don't see any errors in the log

Has anyone experienced this? I am hoping someone can point me to the right direction to fix it.

Cheers,
Michael.

0 Karma

jcoates_splunk
Splunk Employee
Splunk Employee

Hi, IIRC that's the format that you get from CloudTrail when there are multiple accounts writing into one bucket (http://docs.splunk.com/Documentation/AddOns/latest/AWS/ConfigureInputs#CloudTrail_inputs) -- newer versions of the Add-on should parse those records, but an older version would leave the records wrapper on.

0 Karma
Get Updates on the Splunk Community!

New Year. New Skills. New Course Releases from Splunk Education

A new year often inspires reflection—and reinvention. Whether your goals include strengthening your security ...

Splunk and TLS: It doesn't have to be too hard

Overview Creating a TLS cert for Splunk usage is pretty much standard openssl.  To make life better, use an ...

Faster Insights with AI, Streamlined Cloud-Native Operations, and More New Lantern ...

Splunk Lantern is a Splunk customer success center that provides practical guidance from Splunk experts on key ...