You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, you can change HTTPI.log_level to change the log level we are using to log.
if you look at HTTPI.log, it sends the log_level to the Logger.
that's actually what the Logger's severity should be used for. what i did for savon 2.0 (which used the same method before), was to just log with an appropriately low log level like "debug" or "info" and let people change the Logger's severity to specify what they want to see.
The text was updated successfully, but these errors were encountered:
I was thinking in something like you did on savon.
By default have a logger to stdout on info severity. Users can change severity on logger instance, like you said.
Logger be an attribute accessor, so users can change to any logger that wants. File, Syslogger ... etc.
Remove log and log_level attributes. Or warn, and say that will be removed on next version.
About what to log, i can only think on these cases:
Logs all request options using debug severity.
Use something like Common Log Format to log request information using info severity.
Logs response (code, headers, body) using debug severity.
currently, you can change
HTTPI.log_level
to change the log level we are using to log.if you look at HTTPI.log, it sends the
log_level
to the Logger.that's actually what the Logger's severity should be used for. what i did for savon 2.0 (which used the same method before), was to just log with an appropriately low log level like "debug" or "info" and let people change the Logger's severity to specify what they want to see.
The text was updated successfully, but these errors were encountered: