[ 
https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318321#comment-15318321
 ] 

Pavel Tupitsyn edited comment on IGNITE-1629 at 6/8/16 4:06 PM:
----------------------------------------------------------------

Considerations:
* We need a single common point of logging in .NET and Java, so that events 
from both platforms are visible in .NET.
* Implement IgnitePlatformLogger which delegates to .NET
* Do not depend on any library in Core. Provide an ILogger facade similar to 
IgniteLogger in Java
* Provide a default ConsoleLogger in .NET. using native .NET console will fix 
the issue with log not being shown in R# test runner, LINQPad output and other 
places.
* Provide optional integrations with NLog and Log4Net (separate tickets)
* Include ignite-log4j in NuGet package so that native logging can be 
configured via config/ignite-log4j.xml file (see IgnitionEx logic). What is 
ignite-log4j2?


was (Author: ptupitsyn):
Considerations:
* We need a single common point of logging in .NET and Java, so that events 
from both platforms are visible on both platforms
* Implement IgnitePlatformLogger which delegates to .NET
* Do not depend on any library in Core. Provide an ILogger facade similar to 
IgniteLogger in Java
* Provide optional integrations with NLog and Log4Net (separate tickets)
* Include ignite-log4j in NuGet package so that native logging can be 
configured via config/ignite-log4j.xml file (see IgnitionEx logic). What is 
ignite-log4j2?

> .Net: Introduce native logging facility.
> ----------------------------------------
>
>                 Key: IGNITE-1629
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1629
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel Tupitsyn
>            Priority: Blocker
>
> This is pretty serious usability issue. Currently Ignite produces logs using 
> Java "log4j" library. While naural for Java environment, this is somewhat 
> alien for Windows users. 
> We need to investigate ability to hack into normal .Net logging frameworks. 
> This include both native Windows APIs (e.g. events), and widely-used .Net 
> loggers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to