-
Notifications
You must be signed in to change notification settings - Fork 204
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
[docs] Add Native AOT diagnostics support documentation for iOS-like platforms #2614
[docs] Add Native AOT diagnostics support documentation for iOS-like platforms #2614
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ivanpovazan
Thank you @davidbritch! |
|
||
### Observability and telemetry | ||
|
||
Tracing of .NET MAUI applications on mobile platforms is enabled through [dotnet-dsrouter](/dotnet/core/diagnostics/dotnet-dsrouter) which connects diagnostic tooling with .NET applications running on iOS and Mac Catalyst, over TCP/IP. However, Native AOT is currently not compatible with this scenario as it doesn't support EventPipe/DiagnosticServer components built with the TCP/IP stack. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EventPipe remote tracing is not the only "Observability and telemetry" scenario.
I assume that the "Explicitly in code" instrumentation https://learn.microsoft.com/en-us/dotnet/core/diagnostics/observability-with-otel#observability-approaches-in-net still works fine. Is that correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected in: #2619
Summary
This PR adds documentation on Native AOT diagnostics support when targeting iOS-like platforms.
Fixes: dotnet/runtime#106799