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
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 ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...