[jira] [Comment Edited] (IGNITE-5798) Logging Ignite configuration at startup

["Ivan Fedotov (JIRA)" <ji...@apache.org>]

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

Ivan Fedotov edited comment on IGNITE-5798 at 3/22/18 12:54 PM:
----------------------------------------------------------------

[~ein], 

I link log example with toString() method in comment above [1]. Earlier you've said [2] that IgniteConfiguration.toString() will be enough. So, I have several questions:
 # Can you explain properties that you want to see in log?
 # In 2.4 release IgniteConfiguration logging when log.isInfoEnabled() and it doesn't depend on IgniteLogger.quiet[3]. Do you think that it appropriate behavior?

[1]Permalink

[2]                     Permalink

[3]https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java#L1904


was (Author: ivanan.fed):
[~ein], 

I link log example with toString() method in comment above [1]. Earlier you've said [2] that IgniteConfiguration.toString() will be enough. So, I have several questions:
 # Can you explain properties that you want to see in log?
 # In 2.4 release IgniteConfiguration logging when log.isInfoEnabled() and it doesn't depend on IgniteLogger.quiet[3]. Do you think that it appropriate behavior?

[1]Permalink

[2]Permalink

[3]https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java#L1904

> Logging Ignite configuration at startup
> ---------------------------------------
>
>                 Key: IGNITE-5798
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5798
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexandr Kuramshin
>            Assignee: Ivan Fedotov
>            Priority: Major
>              Labels: easyfix, newbie
>
> I've found that IgniteConfiguration is not logged even when -DIGNITE_QUIET=false
> When we starting Ignite with path to the xml, or InputStream, we have to ensure, that all configuration options were properly read. And also we would like to know actual values of uninitialized configuration properties (default values), which will be set only after Ignite get started.
> Monitoring tools, like Visor or WebConsole, do not show all configuration options. And even though they will be updated to show all properties, when new configuration options appear, then tools update will be needed.
> Logging IgniteConfiguration at startup gives a possibility to ensure that the right grid configuration has been applied and leads to better user support based on log analyzing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)