Closed jamescrosswell closed 2 weeks ago
@bitsandfoxes I had a bit of a scan through the MetricAggregator
class but didn't see anywhere obvious to add logging... what additional logging did you want here?
@bitsandfoxes I had a bit of a scan through the
MetricAggregator
class but didn't see anywhere obvious to add logging... what additional logging did you want here?
Initially, I thought that just emitting a metric could leave a log but I can see this getting quite noisy. Then I thought maybe just during flushing but there are already logs there. Now I think the issue came through Unity's logger not being able to handle the logs coming from the background.
@bitsandfoxes I had a bit of a scan through the
MetricAggregator
class but didn't see anywhere obvious to add logging... what additional logging did you want here?Initially, I thought that just emitting a metric could leave a log but I can see this getting quite noisy. Then I thought maybe just during flushing but there are already logs there. Now I think the issue came through Unity's logger not being able to handle the logs coming from the background.
OK, should we bother with this PR or close it do you think? It just adds a log if metrics are disabled... not sure how useful that is.
We'll need to fix the broken verify tests if we want to merge.
It just adds a log if metrics are disabled
How about we do it the other way around and treat it like an integration that logs if it got registered.
Resolves https://github.com/getsentry/sentry-dotnet/issues/3310
skip-changelog