[ Logging properties ] change buffer size for Containers SDOUT


Fabien Guichard
 

Hello,

while developping an extension ofr a buildpack, related to logging event from applications, we found out that STDOUT logs where being flushed with a fixed size (because we're receving troncated strings in our external aggregating system).

it seems to us that the buffer size is around 4000 caracters, which is not what we would like.

We went through doppler metron and loggregator configurations & codes, without success, to find out anything related to fixed-size logging property.

Do ou know where we should go to configure the size of the buffer being flushed please ?

Many thanks for the time you took to read our very first question on this ML.

Regards,
Fabien.


Jim CF Campbell
 

Hi Fabien,

It's a restriction that the Executor component of Diego implements. It's
not in the Loggregator code. I'm not sure of the where or why of it.

Jim


On Thu, Apr 7, 2016 at 6:44 AM, Fabien Guichard <fabien.guichard(a)orange.com>
wrote:

Hello,

while developping an extension ofr a buildpack, related to logging
event from applications, we found out that STDOUT logs where being flushed
with a fixed size (because we're receving troncated strings in our external
aggregating system).

it seems to us that the buffer size is around 4000 caracters, which is not
what we would like.

We went through doppler metron and loggregator configurations & codes,
without success, to find out anything related to fixed-size logging
property.

Do ou know where we should go to configure the size of the buffer being
flushed please ?

Many thanks for the time you took to read our very first question on this
ML.

Regards,
Fabien.


--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963


Eric Malm <emalm@...>
 

Hi, Fabien,

If you're running the buildpack staging tasks on Diego cells, Jim is
correct that the executor's log-streaming system currently imposes a
hard-coded 4-KiB limit on each log line. The Diego team has a story (
https://www.pivotaltracker.com/story/show/111866195) to increase that to 60
KiB that we expect to get to in a few weeks. The original limit was
introduced very early in the life of the executor component, and was likely
based on some too-restrictive assumptions about the maximum size of UDP
datagrams. We've since validated that on Linux and on Windows these
datagrams can contain a little less than 64KiB of data in their payload, so
the 60-KiB limit should be fine.

Thanks,
Eric, CF Runtime Diego PM

On Thu, Apr 7, 2016 at 10:12 AM, Jim CF Campbell <jcampbell(a)pivotal.io>
wrote:

Hi Fabien,

It's a restriction that the Executor component of Diego implements. It's
not in the Loggregator code. I'm not sure of the where or why of it.

Jim


On Thu, Apr 7, 2016 at 6:44 AM, Fabien Guichard <
fabien.guichard(a)orange.com> wrote:

Hello,

while developping an extension ofr a buildpack, related to logging
event from applications, we found out that STDOUT logs where being flushed
with a fixed size (because we're receving troncated strings in our external
aggregating system).

it seems to us that the buffer size is around 4000 caracters, which is
not what we would like.

We went through doppler metron and loggregator configurations & codes,
without success, to find out anything related to fixed-size logging
property.

Do ou know where we should go to configure the size of the buffer being
flushed please ?

Many thanks for the time you took to read our very first question on this
ML.

Regards,
Fabien.


--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963