[
https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196668#comment-16196668
]
Alexandr Kuramshin commented on IGNITE-5798:
--------------------------------------------
Hi, [~ivanan.fed]
1. I think we should use output of {{IgniteConfiguration.toString()}} which
implemented by standard call to
{{GridToStringBuilder#toString(java.lang.Class<T>, T)}}. The maximum
inheritance level will be used. Every object being logged takes own
responsibility to have right {{toString()}} implementation. You may check
proper {{@GridToStringInclude}} and {{@GridToStringExclude}} annotation usage
on all enclosed configuration objects.
2. Null values also should be logged.
3. Relates to question #1.
4. When {{IgniteLogger.quiet == true}} we should not log
{{IgniteConfiguration}}. Only when {{IgniteLogger.quiet == false}}.
> 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)
