Skip to content
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

Merged
merged 1 commit into from
Jun 9, 2021

Conversation

piotradamczyk5
Copy link
Contributor

@piotradamczyk5 piotradamczyk5 commented Jun 7, 2021

Fixes #1958

Test Plan

How do we know the code works?

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

@github-actions
Copy link
Contributor

github-actions bot commented Jun 7, 2021

Timestamp: 2021-06-08 12:34:40
Buildscan url for ubuntu-workflow run 918266850
https://gradle.com/s/76mrlgehvdp7u

@@ -54,7 +55,7 @@ internal fun withGlobalExceptionHandling(block: () -> Int, exitProcessFunction:
}

is InfrastructureError -> {
Copy link
Contributor

@pawelpasterz pawelpasterz Jun 8, 2021

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?

Copy link
Contributor Author

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?

Copy link
Contributor

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...

Copy link
Contributor Author

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

@bootstraponline bootstraponline force-pushed the 1958-change-sentry-events branch from 416d886 to e568d3e Compare June 8, 2021 12:27
@pawelpasterz pawelpasterz enabled auto-merge (squash) June 9, 2021 05:50
@pawelpasterz pawelpasterz merged commit 0143dc1 into master Jun 9, 2021
@pawelpasterz pawelpasterz deleted the 1958-change-sentry-events branch June 9, 2021 07:19
@github-actions github-actions bot locked and limited conversation to collaborators Jun 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Filtering Sentry errors
3 participants