Default configuration outputs redundant access logs (mostly duplicate of RTR logs)

[cloudfoundry]

Default configuration outputs redundant access logs (mostly duplicate of RTR logs)

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/115607207.

[davidjahn]

Hi @gberche-orange , thank you very much for your suggestion to turn off nginx logging by default.

Regarding the container's file system max size being exceeded, I do not believe that this is a problem because the two log files are in fact just named pipes created with mkfifo, and do not persist any data to disk.

However, you are correct that many of the nginx log messages are duplicated by the router log messages, and it might be good decision to turn off nginx logging by default. A story in pivotal tracker has been created automatically, and we will discuss the issue further at our next planning meeting. Thanks again!

[davidjahn]

Hi @gberche-orange , we discussed this issue this morning, and decided that for now we will leave logging turned on by default. There are two reasons for this:

1. Although the most common log messages (e.g., a successful HTTP request) for nginx are duplicated by gorouter logging, there are possible nginx logging messages (for example, errors) that the gorouter will not duplicate.
2. It is possible for the user to turn off logging entirely by adding a custom nginx.conf to an app's root folder.

We don't feel that the gain in performance from turning off logging will outweigh the loss of debugging data for the user.

I am closing the issue for now, but please feel free to comment if you have any additional comments to add.