Skip to content

.NET Profiling for client apps (Desktop/CLI/Mobile) #2315

@bruno-garcia

Description

@bruno-garcia

Follow up from: #1955

Goals:

Followups from: #2206

Some notes:

  • We should support the lowest .NET version possible but for as long as we have no friction to do so. If supporting .NET 6 is the simplest/what we get OOTB, we should take that route. It's a new feature and we expect new customers/those upgrading to take advantage of. in other words: No .NET Framework or unsupported .NET Core as a goal.
  • mark threads that don't run any user code as in-app=false
  • should we filter-out sentry-specific/profiling-specific samples? marked as in-app=false
  • provide debug_meta images if we want to show line numbers - this may need to be opt-in as it will likely add some runtime overhead
  • it may be possible to handle GCstart & GCend events to show garbage collection
  • Figure out thread names (we only have native thread IDs though so it seems to be a problem)
  • Mobile/MAUI is a stretch goal (see: filipnavara/maui-sentry-profile)

Metadata

Metadata

Assignees

Projects

Status

In Progress

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions