Abel Luck <a...@guardianproject.info> writes:
> Thanks Micah, very useful indeed.
> But it only works for nginx' access log, not the error log.
Yep, I forgot to mention that!
> AFAICT from reading the nginx docs , it is only possible to configure
> the error log path and the log level.
> Having access to error logs is useful, arguably more so than the normal
> logs, in order to troubleshoot misconfigurations and identify 404s that
> should or shouldn't be happening.
> Best to disable error logs it seems, and only enable them when debugging.
Its hard to minimize logging, pesky little ips showing up everywhere! In
fact a lot of webapps can take the IPs that are available in the HTTP
headers and store them in their own internal databases for whatever
purposes. Even if you have the access log zeroed out. This is why we use
the apache mod_remove_ip module that will remove them internally before
they get to any application.
List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
To unsubscribe, email: guardian-dev-unsubscr...@lists.mayfirst.org