[
https://issues.apache.org/jira/browse/IGNITE-20569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-20569:
------------------------------------
Release Note: .NET: Use Microsoft.Extensions.Logging APIs for logging.
(was: .NET: Refactor logging to Microsoft.Extensions.Logging)
> .NET: Thin 3.0: Revise logging
> ------------------------------
>
> Key: IGNITE-20569
> URL: https://issues.apache.org/jira/browse/IGNITE-20569
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Affects Versions: 3.0.0-beta1
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Blocker
> Labels: .NET, ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> .NET client in Ignite 3.x uses custom *IIgniteLogger* interface. This
> approach is copied from 2.x client; it is outdated and inefficient.
> Revise it:
> * Should we add a dependency on
> [Microsoft.Extensions.Logging.Abstractions|https://www.nuget.org/packages/Microsoft.Extensions.Logging.Abstractions/6.0.4#dependencies-body-tab],
> and use standard *ILogger* instead (accept *ILoggerFactory* in config)?
> * Without that, how do we support structured logging, templates,
> code-generated loggers?
> * How do we integrate with popular loggers? With *ILogger* it comes out of
> the box.
> See *Logging guidance for .NET library authors*:
> https://learn.microsoft.com/en-us/dotnet/core/extensions/logging-library-authors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
