Thats a good idea...We need to make sure, if there are any internal scripts
that are dependent on the log level gets changed and document (and
highlight) the behavior so that if customers have their scripts, alert
notifications; they modify those...
-Anil.
On Thu, Mar 16, 2017 at 7:50 PM, Jinmei
Looks like our log files in the end, still print out the geode log levels
like "fine" for "debug", "error" for "fatal". This is because when
developer wrote
"logger.debug("message")" in their code, the appender we used will
internally convert that log message to print out "fine" instead of
"debug".
Since we have trace for finer and finest I think all is well.
On Thu, Mar 16, 2017 at 1:38 PM, Kirk Lund wrote:
> That's correct. I flipped mine around half way down the list. I love to
> delete the old LogWriter log levels to eliminate this confusion...
>
>
> On Thu, Mar 16, 2017 at 1:12 PM, Ji
That's correct. I flipped mine around half way down the list. I love to
delete the old LogWriter log levels to eliminate this confusion...
On Thu, Mar 16, 2017 at 1:12 PM, Jinmei Liao wrote:
> I believe this is the mapping:
>
> LogWriter Log4J2
>
I believe this is the mapping:
LogWriter Log4J2
---
SEVERE= FATAL
ERROR = ERROR
WARNING = WARN
INFO, CONFIG = INFO
FINE = DEBUG
FINER, FINEST = TRACE
We do have a lot of c
Here's the equivalent log levels between LogWriter levels and Log4J2 levels
LogWriter Log4J2
SEVERE= FATAL
ERROR = ERROR
WARN = WARNING
INFO = INFO, CONFIG
DEBUG = FINE
TRACE = FINER, FINEST
On Thu, Mar 16, 2017 at 10:08 AM, Darrel Schneider
w
Do we still have lots of code that is deciding whether or not to log based
on finest, finer and fine, etc?
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: +1-631-835-4771
On Thu, Mar 16, 2017 at 1:08 PM, Darrel Schneider
wrote:
> My understanding is the geode fine, finer, fin
My understanding is the geode fine, finer, finest all map to log4j debug.
If we get rid of the geode levels would all three fine* levels be enabled
when the log level is debug?
If so this might be a problem because finest can be way too much.
I think geode's config and info both map to log4j info
+1 to making the change and updating the docs to reflect only the new log
levels.
On Wed, Mar 15, 2017 at 10:45 AM Jinmei Liao wrote:
> Hi, all,
>
> Geode, before using log4j for logging has implemented its own LogWriters
> and logLevels. Geode log levels has values like "finest, finer, fine,
>
Hi, all,
Geode, before using log4j for logging has implemented its own LogWriters
and logLevels. Geode log levels has values like "finest, finer, fine,
config, info, warning, error, severe". We've moved away from using these
log writers to favor using log4j logging. So, mostly, geode logs have lo
10 matches
Mail list logo
