Getting Data In

Splunk HEC not parsing out separate events from aws cloudwatch aws config logs

kaydub00
Explorer

I followed this documentation on setting this up: https://aws.amazon.com/blogs/mt/ingest-aws-config-data-into-splunk-with-ease/

We are on Splunk Enterprise 7.1.3.

Sometimes our data is parsed properly, but I've noticed that on many occasions multiple events get forwarded to HEC and HEC can't properly parse them. These multiple events end up as just raw input in splunk when I need splunk to intelligently parse this info.

I have setup a lambda function on my kinesis stream so I can manually parse this, I'm also considering splitting the records up and making sure only one record gets forwarded to Splunk at a time and then I'll throw the extra messages back into the kinesis stream but that feels like a really bad hack. Not sure what I can do to fix this, has anyone else had this issue and have a solution?

Tags (1)
0 Karma

kaydub00
Explorer

I got this fixed. We had to add the firehose add-on and then change the input type to firehose:json

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!

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...