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
This is creating a lot of noise in my servers because I use sentry-log, which sends an error event to a sentry server each time something is logged at error! level. This wouldn't affect only this particular case, as any monitoring tool that parses and notifies on errors logged in stdout will suffer from the same amount of false positives.
As far as I understand logging levels, not every response with errors is an error in itself. Anything that in a HTTP server has status lower than 500 is not an error to be concerned about. For example:
user submits form with invalid values
someone tries to log in with wrong credentials
etc.
Is changing the log level to info! something that could be considered? I could implement my own Logger extension but I guess other users may benefit from this change too
The text was updated successfully, but these errors were encountered:
Description of the feature
In the default logger, any graphql that responds with errors is logged at error level: https://github.com/async-graphql/async-graphql/blob/master/src/extensions/logger.rs#L68
This is creating a lot of noise in my servers because I use sentry-log, which sends an error event to a sentry server each time something is logged at
error!
level. This wouldn't affect only this particular case, as any monitoring tool that parses and notifies on errors logged in stdout will suffer from the same amount of false positives.As far as I understand logging levels, not every response with errors is an error in itself. Anything that in a HTTP server has status lower than 500 is not an error to be concerned about. For example:
Is changing the log level to
info!
something that could be considered? I could implement my own Logger extension but I guess other users may benefit from this change tooThe text was updated successfully, but these errors were encountered: