Getting Data In

Best practices for logging large events (SOAP requests with included Base64 encoded documents)

New Member

We need to log all data traffic from SOAP interfaces with large requests/responses, which sometimes contain included Base64 encoded documents. The log events are up to 20 MB.
It that possible without performance impacts or should we filter the messages before they are forwarded to the indexer and send them to another storage (f.i. S3)? We need all this events in Splunk, but it would be sufficient to have references to the encoded documents.
Does anyone have experience with forwarding/logging huge events?

Our Splunk volume license wouldn't be a problem, we have a contract of about 100 GB daily für Splunk AWS.

Falk Berger

0 Karma
Get Updates on the Splunk Community!

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...

Reminder! Splunk Love Promo: $25 Visa Gift Card for Your Honest SOAR Review With ...

We recently launched our first Splunk Love Special, and it's gone phenomenally well, so we're doing it again, ...