-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve access logging #712
Comments
Conclusion from my research:
|
Part of #712 Log path starting with `syslog:` or `memory:` is not relative path, but has to be passed to nginx unchanged.
So, regarding the format, we decided to wait for the next release of OpenResty (see @mikz comment above). Enabling/Disabling the service can be done with the policy introduced in #856 , and APIcast can be configured to log to syslog using an ENV. I think there's nothing else we need to do for 2.3, so I'll remove this issue from the milestone. |
ACK. Will update THREESCALE-1148 accordingly. |
hi @mikz Is it possible to expect this feature as a policy? |
Done in #1089 |
Use Cases
Details
access_log
directive offersif
to enable/disable logging by setting a variable to 0/1 - this can be used to enable/disable logging by a policy.It is possible the
path
parameter of theaccess_log
directive can be a variable too and can be controlled from within a policy. Then we should consider usingopen_log_file_cache
to files opened.Syslog can be either achieved by setting
syslog:
path to theaccess_log
directive, or we have to reuse https://github.com/nmasse-itix/apicast-logger to offer syslog from a policy.Custom formats can be defined by
log_format
directive pointing just to a variable that is later populated by a policy.The text was updated successfully, but these errors were encountered: