file configuration,
> so they show less details.
>
> Thank you,
> Alexey
>
> From: Nikolai Tikhonov
> Sent: Friday, December 1, 2017 5:21 PM
> To: dev@ignite.apache.org
> Subject: Re: Ignite Logger & logging file config output
>
> Alexey,
>
> Lo
rigorously: Windows 10 10.0
> amd64. Our team will appreciate the feedback if you experience any problems
> running ignite in this environment.
> 2017-12-01T17:06:49,436][INFO ][main][IgniteKernal%verboseLogGrid] 3-rd
> party licenses can be found at: C:\incubator-ignite\libs\licenses
>
; amd64. Our team will appreciate the feedback if you experience any problems
> running ignite in this environment.
> 2017-12-01T17:06:49,436][INFO ][main][IgniteKernal%verboseLogGrid] 3-rd
> party licenses can be found at: C:\incubator-ignite\libs\licenses
>
> Thank you,
> Alexey
Denis Magda
Sent: Tuesday, November 21, 2017 2:01 AM
To: dev@ignite.apache.org
Subject: Re: Ignite Logger & logging file config output
Good point. Could you create a ticket and probably contribute this improvement?
—
Denis
> On Nov 20, 2017, at 3:12 AM, Alexey Popov <tank2.a.
Good point. Could you create a ticket and probably contribute this improvement?
—
Denis
> On Nov 20, 2017, at 3:12 AM, Alexey Popov wrote:
>
> Hi Igniters,
>
> Could you please advise why Ignite does not indicate
> 1) the logger type it uses
> 2) the logger
Hi Igniters,
Could you please advise why Ignite does not indicate
1) the logger type it uses
2) the logger configuration file (name) it applies
during startup?
Can we add such output to IgniteLogger implementations?
Thanks,
Alexey
--
Sent from: