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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...