Hi Scott,

hope you're doing well.

The error_log directive is documented well [1].
There's no format of error messages.

While I'm here I'd recommend to keep 72 characters per line, that helps
a lot to read emails, thank you.

References:
[1] https://nginx.org/en/docs/ngx_core_module.html#error_log

--
Sergey A. Osokin

In-Reply-To: <MW3PR12MB44274FA60D2AB99FB5860213F4ED9@MW3PR12MB4427.namprd12.prod.outlook.com>

On Tue, Apr 12, 2022 at 03:29:57PM +0000, Scott Snow wrote:
> Is there documentation for the format of error messages nginx posted to error_log?
> Specifically, following the level in square brackets are two numbers separated by '#'; what do these represent?
> For instance, the message on the page Advanced Configuration with Snippets | NGINX Ingress Controllerhttps://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-snippets/ begins with "[emerg] 31:31:"
> Why I'm asking is for purposes of documentation; a system using nginx routes these messages to syslog; the design document for the module responsible for publishing the messages gives the format and examples. The example for nginx errors begins:
> <131>Oct 24 18:17:47 imx7d-zoll-resus nginx: 2018/10/24 18:17:47 [error] 3105#0: *11 connect() failed (111: Connection refused) while connecting ...
>
> We have a format and examples for each of syslog-ng, gunicorn access, gunicorn error, and nginx access.
_______________________________________________
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-leave@nginx.org