Getting Data In

Firehose through HTTP Event Collector generates duplicate log records

mmkt
Loves-to-Learn

Hello everyone,

I am streaming CloudWatch logs to SPLUNK through Firehose, and I faced the following issue:

Some json records are being indexed(?) twice and show up twice in search. The only difference between the records is the time of indexing.
I am trying to figure out how I can debug the issue. Record shows up only once in source log group in cloudwatch and s3 backups. It’s either Firehose sending a particular record twice or SPLUNK processing the same record two times. Do you have an idea how I can check my theories? I didn’t find much useful info in splunk http event collector logs. It has only technical info about the transaction: size/speed/time.

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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...