[ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189346#comment-16189346 ]
Ivan Fedotov commented on IGNITE-5798: -------------------------------------- Hello! Now I’m working at ticket #5798 “Logging Ignite configuration at startup” and have the following questions: 1.Should I get fields and their values only from IgniteConfiguration or I should also get them from inherited classes? If second variant is correct , what level of inheritance should I use? 2.Should I log fields with null values? 3.Is format [field] : [value.toString] appropriate? Or [field] : [GridToStringBuilder.toString(value)] is better? 4.About “I’ve found that IgniteConfiguration is not logged even when -DIGNITE_QUIET=false”. Does it mean that I should log IgniteConfiguration when log.isQuiet = false to the file and terminal? > 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 > 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 (v6.4.14#64029)