Discuss the next plan for skyapm-dotnet

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Discussion
• Bug
• Requirement
• Feature or performance improvement

---

Hi, community, SkyApm-dotnet client provides proven tracing capabilities for .NET Core applications, and recently, @GeorGeWzw has implemented the integration of Microsoft.Extension.Logging and Skywalking (https://github.com/SkyAPM/SkyAPM-dotnet/pull/502 ) . So, where should we go next ?

Here are some of my thoughts,

1. Integrate System.Diagnostics.Metrics API to provide the ability to report meters to skywalking.
2. Integrate System.Diagnostics.Activity API as another implementation of trace.
3. Exploring the implementation of using clr-profiler as an auto-instrument, you can refer to opentelemetry-dotnet-instrumentation , and I noticed that ManagedDotnetProfiler provides a possibility to implement clr-profiler in C# instead of C++.
4. When I started to develop skyapm-dotnet 5 years ago, the kernel implementation of tracingcontext almost completelyreferenced java-agent, and now it seems to be possible to consider refactoring using the new API of .NET 5/6, such as using Span<T> to improve performance.

Any ideas are welcome.

[sampsonye]

1. Support More Middleware like redis、Oracle and so on
2. Support Method StackFrame Tracing

[wu-sheng]

Today, there was an asking for auto-instrumentation in the ASF skywalking channel.