-
Notifications
You must be signed in to change notification settings - Fork 119
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
feat: Set Google api issues level as DEBUG #2016
Conversation
Timestamp: 2021-06-08 12:34:40 |
@@ -54,7 +55,7 @@ internal fun withGlobalExceptionHandling(block: () -> Int, exitProcessFunction: | |||
} | |||
|
|||
is InfrastructureError -> { |
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.
Do we want to change log level for FTLError
as well?
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.
I am not sure, does FTLError occurs only on Google Api issues?
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.
According to error description, it's thrown when an internal error occurs.
So I guess you are right...
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.
we could leave it for now and see later how it is working
416d886
to
e568d3e
Compare
Fixes #1958
Test Plan
When a Google infrastructure issue occurs(FlankGoogleApiError, InfrastructureError) it is logged with log level DEBUG.
You could throw this exception on your own
InfrastructureError("test").report(SentryLevel.DEBUG)
. This feature will be used for creating Sentry notification about critical errors to the newly created channel#sentry-errors