Perhaps this can be useful for you:
https://github.com/Lax/nginx-http-accounting-module

Kind regards,
Oscar

On Wed, Apr 11, 2018 at 6:19 AM, Jeff Abrahamson <jeff@p27.eu> wrote:

> I want to monitor nginx better: http returns (e.g., how many 500's, how
> many 404's, how many 200's, etc.), as well as request rates, response
> times, etc. All the solutions I've found start with "set up something to
> watch and parse your logs, then ..."
>
> Here's one of the better examples of that:
>
> https://www.scalyr.com/community/guides/how-to-
> monitor-nginx-the-essential-guide
>
> Perhaps I'm wrong to find this curious. It seems somewhat heavy and
> inefficient to put this functionality into log watching, which means
> another service and being sensitive to an eventual change in log format.
>
> Is this, indeed, the recommended solution?
>
> And, for my better understanding, can anyone explain why this makes more
> sense than native nginx support of sending UDP packets to a monitor
> collector (in our case, telegraf)?
>
> --
>
> Jeff Abrahamson
> +33 6 24 40 01 57
> +44 7920 594 255
> http://p27.eu/jeff/
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>



--
Oscar Fernandez Sierra
oscaretu@gmail.com
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx