Welcome! Log In Create A New Profile

Advanced

Re: $time_iso8601 is not set for invalid HTTP?

Darren Pilgrim
December 01, 2014 11:26AM
On 12/1/2014 5:23 AM, igorb wrote:
> Maxim Dounin wrote:
>
>> Use map instead:
>
> Thanks, map works nicely :)
>
>> avoid using such "timestamped log names" at all as this approach implies
> unneeded overhead on opening/closing files for each request.
>
> I use open_log_file_cache to mitigate this. Are there still problems with
> that? I would prefer to keep things simple and avoid explicit log rotation.
> The latter requires in my case more setup over a simple Docker container
> with just nginx and extra log processing to extract monthly logs to feed
> those to webalizer.

If you're using Docker, use the Docker log collector, use the syslog
patch for nginx and have it log externally, or create a volume for the
logs and a helper container in which you run the log tools. It really
should not be nginx's or its container's job to manage/rotate logs.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

$time_iso8601 is not set for invalid HTTP?

igorb November 29, 2014 03:48PM

Re: $time_iso8601 is not set for invalid HTTP?

Maxim Dounin December 01, 2014 07:54AM

Re: $time_iso8601 is not set for invalid HTTP?

igorb December 01, 2014 08:23AM

Re: $time_iso8601 is not set for invalid HTTP?

Maxim Dounin December 01, 2014 10:56AM

Re: $time_iso8601 is not set for invalid HTTP?

Darren Pilgrim December 01, 2014 11:26AM

Re: $time_iso8601 is not set for invalid HTTP?

Oleksandr V. Typlyns'kyi December 01, 2014 12:42PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 128
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready