Getting Data In

K8 AWS HF Delays / Timeouts

lavster
Path Finder

Hello, We are wondering if anyone else has experienced issues using a k8 cluster of heavy forwarders, to receive AWS firehose data into a GCP Splunk enterprise setup via HEC. However we are seeing lots of duplicates of the data and also a flip on that, some timeouts meaning the event is sent to the s3 bucket rather than being ingested in Splunk.

We thought this was an isolated issue in our setup, so we setup a pre-prod environment with the same setup and the same problem is occurring.

Labels (1)
0 Karma
Get Updates on the Splunk Community!

Alpha Launch: AI-Assisted Auto-Schematization for CIM

Streamlining Data Onboarding: Announcing the Alpha Release of AI-Assisted Auto-Schematization For many Splunk ...

Enterprise Security(ES) Essentials or Premier? Let's discuss Splunk ES Editions on ...

  Hi everyone, Last year at .conf25, we shared something exciting: Splunk Enterprise Security is evolving ...

[Puzzles] Solve, Learn, Repeat: Advent of Code - Day 5

Advent of CodeIn order to participate in these challenges, you will need to register with the Advent of Code ...