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
Server Access Log #69
Comments
Id -> 58266a50d73408ce4f3546ba |
Just added you into the dev channel. |
Since we have made headway, this (https://github.com/go-aah/tools/blob/v0-unstable/aah/app-template/config/aah.conf.atmpl#L109-L123) would also have to be updated... At least it should contain |
You're correct, after merging your PR, Then |
Signed-off-by: Lanre Adelowo <me@lanreadelowo.com>
To manage server effectively it is necessary to know details about the request, response, processing time, client IP address, etc. aah framework provides the flexible and configurable access log capabilities.
aah server logs the details based on log flags. Flag format usage is
%flagname
The available flags as follows:
clientip
- Client IP address aka Remote IP addressreqtime
- Time of request is recevied by server. Local time in default format RFC3339 or you can provide onerequrl
- Request URL not including query stringreqmethod
- Request HTTP methodreqproto
- Request Protocol. For e.g:HTTP/1.1
,HTTP/2.0
reqid
- It logs request id otherwise it logs-
. Referrequest.id.header
config in theaah.conf
reqhdr:<header_name>
- To log request header, if not available-
is loggedquerystr
- To log request query string if available otherwise-
is loggedresstatus
- Response Statusressize
- Bytes sent, excluding response HTTP headers, otherwise-
if no bytes were sentreshdr:<header_name>
- To log response header, if not available-
is loggedrestime
- Request processing time (in milliseconds), time elapsed between the request recevied by server and the last bytes were written on the wire by servercustom
- Add non-space string into log stringAccess log processing should not affect the app perfomance.
Access Log Configuration:
The text was updated successfully, but these errors were encountered: