Overly verbose logging that does not have "interesting" information and insufficient logging that does have one has been a long running issue and a common mistake in the industry. We can do better and avoid it by properly integrating OpenTelemetry hooks instead for the end users that want more detailed and configurable tracing experience.
I am yet to look into its API but given there are articles that discuss its integration into standard ASP.NET Core services, I think it can be relevant to this library.
Overly verbose logging that does not have "interesting" information and insufficient logging that does have one has been a long running issue and a common mistake in the industry. We can do better and avoid it by properly integrating OpenTelemetry hooks instead for the end users that want more detailed and configurable tracing experience.
I am yet to look into its API but given there are articles that discuss its integration into standard ASP.NET Core services, I think it can be relevant to this library.