-
Notifications
You must be signed in to change notification settings - Fork 0
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
PB-1351 Log requests and errors to ECS #68
Conversation
e4f308d
to
85a7e05
Compare
5b0f45c
to
708ea45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but not sure if we need to already think about preventing logging credentials (for example the values of Authorization
headers?
4eea02c
to
1e4227f
Compare
Send all API requests as well as the errors to the logging facility
It's already done in settings base
There was a distinction between 200s and 300s, but it resulted in both logging on level `info`, thus squashing these log calls
1e4227f
to
8c0d075
Compare
Also not sure about other Header Content, e.g. Set Cookie (https://security.stackexchange.com/questions/249442/storing-session-id-in-application-logs) |
Can we define which headers we want to log? It just feels unsafe to generally write all headers to the log |
5932f25
to
cae7d76
Compare
2326698
to
85a3a25
Compare
Provide a white list that can be overwritten by the environment for which headers we allow to go to the log
85a3a25
to
1a1d76f
Compare
Install ecs logging package and start sending log entries from the requests to our elastic stack