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
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.    Watch On-Demand   In this Tech Talk, Splunk platform specialists ...

How to Break a Kubernetes Pod on Purpose and Let the AI Troubleshooting Agent Find ...

Let's say I've just rolled out a Kubernetes Deployment with a typo in the image tag. Nothing explodes. The pod ...

Splunk Add-on for Microsoft Windows 11.0.3: Parse Once, Search Faster

The updated Splunk Add-on for Microsoft Windows helps customers search Windows events faster by reducing ...