-
-
Notifications
You must be signed in to change notification settings - Fork 55
Configurable Unity Log level to Event and Breadcrumb #60
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
Comments
+1 would like to limit reporting only to exceptions, errors still to be in breadcrumbs though. |
This should mirror the behavior we have with |
Still want to see this. Unity developers rely on many 3rd party sdk's and generally error log is used as a "serious" log when something has gone wrong but hasn't actually broken the app and sometimes we cant change the code (or at least shouldn't have to since we'll need to update it later and make those changes again). All you need to do is push Exception's over to Fatal and keep Errors as Errors and we can filter out on before send |
You basically just want to be able to automatically separate exceptions from logged errors. I think everything should be in place within the |
This issue describes this todo:
sentry-unity/src/Sentry.Unity/SentryInitialization.cs
Lines 158 to 159 in d30c776
We should have a configurable minimum level for what becomes a breadcrumb and what becomes an event.
Similar to what other logging integrations do.
Example:
https://github.com/getsentry/sentry-dotnet/blob/357a0eb751414ca5cd7a8a1a476fdf5fa309bcb9/src/Sentry.Extensions.Logging/SentryLogger.cs#L119
and
https://github.com/getsentry/sentry-dotnet/blob/357a0eb751414ca5cd7a8a1a476fdf5fa309bcb9/src/Sentry.Extensions.Logging/SentryLogger.cs#L138
The text was updated successfully, but these errors were encountered: