Hey all,
We've written a module to connect NGINX / OpenResty with ZMQ endpoints
(https://github.com/neloe/ngx_zmq), but all requests through the module
report a 0.000 time back to access.log, making it impossible to determine
which of our subsystems is the problem area in terms of latency. Is ther
Hey Baroc,
I know it's now two years but maybe you found a solution for this problem?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,232525,255248#msg-255248
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/ng
Today Dec 1, 2014 at 08:24 Darren Pilgrim wrote:
> 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 c
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 the
Hello!
On Mon, Dec 01, 2014 at 08:23:53AM -0500, igorb wrote:
> > 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
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 pr
Hello!
On Sat, Nov 29, 2014 at 03:48:24PM -0500, igorb wrote:
> I use the if trick to get timestamped log names:
>
> if ($time_iso8601 ~ "^(\d{4})-(\d{2})") {
> set $year $1;
> set $month $2;
> }
>
> access_log .../access-$year-$month.log combined;
>
> However, with nginx/1.4.6 (Ub
