Getting Data In

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

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

Regards,
Falk Berger

0 Karma
Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...