[
https://issues.apache.org/jira/browse/GEODE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123441#comment-16123441
]
Avinash Dongre edited comment on GEODE-258 at 8/11/17 2:47 PM:
---------------------------------------------------------------
Hi [~klund] and [~upthewaterspout]
I have question regarding the Mapping of Log Levels .
Following is what I think should be mapping, please do correct me .
||Log4j Levels||Geode Logger Levels||
|ALL|ALL_LEVEL|
|DEBUG |????|
|ERROR |ERROR_LEVEL|
|FATAL| SEVERE_LEVEL|
|INFO |INFO_LEVEL|
|OFF |NONE_LEVEL|
|TRACE |FINER_LEVEL ???|
|TRACE_INT |FINEST_LEVEL ??? |
|WARN |WARNING_LEVEL|
I am not sure about the mapping for following levels.
* FINEST_LEVEL
* FINE_LEVEL
* CONFIG_LEVEL
* NONE_LEVEL
Also should these level be introduced on gfsh
was (Author: adongre):
Hi [~klund] and [~upthewaterspout]
I have question regarding the Mapping of Log Levels .
Following is what I think should be mapping, please do correct me .
||Log4j Levels||Geode Logger Levels||
|ALL|ALL_LEVEL|
|DEBUG |????|
|ERROR |ERROR_LEVEL|
|FATAL| SEVERE_LEVEL|
|INFO |INFO_LEVEL|
|OFF |NONE_LEVEL|
|TRACE |FINER_LEVEL|
|TRACE_INT |FINEST_LEVEL
|WARN |WARNING_LEVEL|
I am not sure about the mapping for following levels.
* FINEST_LEVEL
* FINE_LEVEL
* CONFIG_LEVEL
* NONE_LEVEL
Also should these level be introduced on gfsh
> Remove deprecated Cache.getLoggerI18n and getSecurityLoggerI18n methods
> -----------------------------------------------------------------------
>
> Key: GEODE-258
> URL: https://issues.apache.org/jira/browse/GEODE-258
> Project: Geode
> Issue Type: Sub-task
> Reporter: Darrel Schneider
> Assignee: Avinash Dongre
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Remove the deprecated Cache.getLoggerI18n and getSecurityLoggerI18n methods.
> All calls can be replaced with getLogger().convertToLogWriterI18n() so this
> should be a quick task.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
