[sentry_logging] Create separate Sentry issues for each distinct event level log

[kaciula]

Problem Statement

I've added the LoggingIntegration from sentry_logging and I'm using Logger.severe to create warning issues in Sentry. The problem is that all calls add events to a single Sentry issue with the same strack trace:

Thread: main
#0 (<asynchronous suspension>)
#1 (<asynchronous suspension>)
#2      LoggingIntegration._onLog (package:sentry_logging/src/logging_integration.dart:87)

I would have expected that each distinct Logger.severe call creates a separate Sentry issue so I can track and resolve them independently.

Solution Brainstorm

Create distinct stack traces based on where the logging call was made from. This would lead to distinct Sentry issues.

Are you willing to submit a PR?

None

[linear]

DART-304

[buenaflor]

@kaciula hey, I took a quick look and we use the stacktrace as given by the logging framework which can sometimes be empty / null if you either don't pass a stacktrace to the log or did not define recordStackTraceAtLevel = Level.severe for example.

Internally we do best effort and call StackTrace.current ourselves when capturing the event since we don't have anything else to work with which is not always the most accurate.

I'd suggest doing this

final log = Logger('Logging');
// either set the record stacktrace level
recordStackTraceAtLevel = Level.SEVERE;

// now the logging framework internally will call StackTrace.current
log.severe('My Logging test');

// or manually pass the stacktrace at the callsite
log.severe('My Logging test', error, StackTrace.current);

[buenaflor]

IMO we should document this better and maybe add a debug log to make it visible that no stacktrace was provided

[kaciula]

Thanks. Now I understand how to properly use this.

[buenaflor]

Will keep this issue open for tracking docs changes