Getting Data In

Maximum SPLUNK_LOGGING_DRIVER_BUFFER_MAX Value

marfass
New Member

When using the Splunk Logging Driver for Docker, you can leverage SPLUNK_LOGGING_DRIVER_BUFFER_MAX to set the maximum number of messages held in buffer for retries. The default is 10 * 1000 but can anyone confirm the maximum value that can be set?

Labels (1)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

It would help if you told us where this setting is. You can't expect us to know everything that has the word "splunk" anywhere and be able to administer anything you throw at us. Yes, we're good but maybe not that good 😉

0 Karma

marfass
New Member

Apologies - you are right! Added context. This is in relation to the Splunk Logging Driver for Docker. Thanks!

0 Karma

PickleRick
SplunkTrust
SplunkTrust

I suppose it's more of a Docker question than a Splunk one. Having said that, I'd expect it to have no "practical" max value. It's probably more of a performance/resources thing (if you set it too high and let it gather those undeliverable messages you could hit OOM-killer and such).

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!

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...

The Data Connection - October 2026

We all have data. Lots of it. But that’s not the problem – it’s understanding what we should we do with it, ...

Beyond the Acceleration Zone: Maximizing Your Success with Splunk Customer Experience ...

Customer success is built on tailored guidance and accessible resources. As a Splunk user, you are encouraged ...