getsentry / getsentry/sentry-dotnet

LogCritical with exception instance has no detail about the exception

Open
#4,822 3 comments 1 reaction 1 assignee Claimed by @Flash0ver View on GitHub
.NET Bug Logs
Dominant language
C#
Stars
770
Forks
248
Avg merge
3d 4h
Merged PRs (30d)
49

Description

Logs: https://nugettrends.sentry.io/explore/logs/?logsFields=timestamp&logsFields=message&logsSortBys=-timestamp&mode=samples&project=1266316&project=1266317&statsPeriod=1h

### Package

Sentry

### .NET Flavor

.NET

### .NET Version

10.0.1

### OS

Linux

### OS Version

_No response_

### Development Environment

Other

### SDK Version

6.0.0

### Self-Hosted Sentry Version

_No response_

### Workload Versions

I see only the message, but I also capture the Exception instance:

https://github.com/dotnet/nuget-trends/blob/49e4745082fa4367b9ab121850f57cfc465f8a40/src/NuGetTrends.Scheduler/DailyDownloadWorker.cs#L200

Why could that be? Shouldn't there be at least the exception message if not the full stack trace?
Image

I tried looking at the trace and I don't see anything linked to it, not even other logs which is odd:

Image

### UseSentry or SentrySdk.Init call

https://github.com/dotnet/nuget-trends/blob/49e4745082fa4367b9ab121850f57cfc465f8a40/src/NuGetTrends.Scheduler/Program.cs#L59-L80

### Steps to Reproduce

logging a failure as described

### Expected Result

find out what's the exceptiion about

### Actual Result

as described

Also: This template for ticket is painfully long. Are folks filing out everything? Note that the "Dev IDE one has Visual Studio selecte by default so those that don't bother changing will misreport it. Consider having another default

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.