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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...