Logging all requests onNginx

Jeff Dyke jeff.dyke at gmail.com
Wed Apr 19 23:53:57 UTC 2017


untested, but if you set error_log to the correct level, it should log
there as it likely received a > 300 response from the backends. I don't
think you want these in your access logs, but i am suprised you don't get
some sort of non < 400 response in those logs.  But it's been a long day....

On Wed, Apr 19, 2017 at 7:06 PM, Alex Samad <alex at samad.com.au> wrote:

> Will it not be logged as a timeout either in access or error/log ?
>
> On 20 April 2017 at 03:46, aT <atif.ali at gmail.com> wrote:
>
>> HI ,
>>
>> Is there a way to log all incoming requests on Nginx .
>>
>> Regardless of them being served or not .
>>
>> For example,  In case of surge of crawler hits , if the upstream backend
>> cannot perform and requests hang  , nginx will not log any such failed
>> request .
>>
>> How can we log them to have more detail on the surges of requests.
>>
>> Thanks
>>
>>
>>
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20170419/38370d76/attachment-0001.html>


More information about the nginx mailing list