The state of logging about s6-overlay

[glerchundi]

https://github.com/just-containers/nginx-loadbalancer as an example to configure logging (the s6-overlay 'way' I guess)

yes :-)

But I have some questions. How do I get this to hit stdout, rather than, or concurrently hitting the file as it does now? Also, what is the benefit to setting up the logging as per the nginx-loadbalancer example? I must admit, it was a lot of work to get the logging setup.

Take it with a grain of salt, it's not finished yet! This is another interesting reading about how @skarnet understands logging: http://skarnet.org/software/s6/s6-log.html (section 'why another logging...).

But being short, I want to achieve the following:

• don't mix different kind of logs into the same place. Because I want to forward them tagged to another centralised log management server. for example, i use different type of logstash configurations for access and error logs.
• i want to have log rotator as a first citizen inside the container, s6-log already provides that (although it's not used in the nginx-loadbalancer yet...)
• just log to stdout supervision level logs, startup and finish.

[smebberson]

@glerchundi, thanks for getting back to me. So there is no real way to achieve it at this point? Is there something in https://github.com/just-containers/nginx-loadbalancer/blob/master/rootfs/etc/services.d/nginx-access-log/run that I can piggy back to output to stdout too (using s6-echo or something)?

[dreamcat4]

On Thu, Apr 23, 2015 at 7:52 AM, Gorka Lerchundi Osa <
[email protected]> wrote:

• just log to stdout supervision level logs, startup and finish.

i want to have log rotator as a first citizen inside the container, s6-log
already provides that (although it's not implemented yet...)

It would also be nice to see a log rotated docker logging plugin.

[glerchundi]

@glerchundi, thanks for getting back to me. So there is no real way to achieve it at this point? Is there something in https://github.com/just-containers/nginx-loadbalancer/blob/master/rootfs/etc/services.d/nginx-access-log/run that I can piggy back to output to stdout too (using s6-echo or something)?

although I would encourage you not to do that, it can be achieved by:

• remove /etc/cont-init.d/00-initialize-log-fds
• remove /etc/services.d/nginx-access-log & /etc/services.d/nginx-error-log
• change these lines, and point to /dev/stdout

done.

[glerchundi]

It would also be nice to see a log rotated docker logging plugin.

yes it would be nice but that probably doesn't solve merging/syslog problem, that's why I really like having switching (through fifos and s6-fdholderd) & logrotation mechanisms inside the container.

[jprjr]

@glerchundi I would love to hear about your logstash setup - do you keep logs at a volume, and have another container accessing the logs?

[glerchundi]

That's it.

[glerchundi]

@jprjr I didn't make it a reality yet but this is my idea:

• CoreOS
• Each machine running CoreOS will have a persistent storage in which containers will place its logrotated logs.
• Use kubernetes to make packages of containers using pods like:
  • nginx-loadbalancer
  • logstash-forwarder

So that every container would have a logstash-forwarder alongside it.

[glerchundi]

@smebberson could I close this?

[smebberson]

Yep. Thanks for getting back to me on it too. I haven't tried it yet, but will shortly.

Sent from my iPhone

On 24 Apr 2015, at 8:13 pm, Gorka Lerchundi Osa [email protected] wrote:

@smebberson could I close this?

—
Reply to this email directly or view it on GitHub.