Allow disabling of specific levels per-logger.

[matt-holden]

My team's usage of LumberJack had the following setup:

• four loggers, DDTTYLogger and DDFileLogger, a crash logger, and an
  analytics logger
• globally-defined ddLogLevel = LOG_LEVEL_DEBUG

Our file logger is added with LOG_LEVEL_INFO.
Our TTY logger is added with LOG_LEVEL_DEBUG.

We use "INFO" events HEAVILY, as they are placed in the file logger and
crash logger to help us know everything that happened leading up to a
bug.

As a requirement, The file logger CANNOT log DEBUG events.

At the same time, because we have such a high volume of INFO events, it
is challenging to see any of the DEBUG events in the TTY logger.

We need to be configure our DDTTYLogger to at the DEBUG level, but omit INFO events.

Essentially: [DDLog addLogger:ttyLogger withLogLevel:(LOG_LEVEL_DEBUG & (~LOG_FLAG_INFO)];

However, this isn't possible in the current implementation of
+[DDLogger lt_log]

When iterating through registered loggers, lt_log:
performs the check, "if (logMessage->logFlag > loggerNode.logLevel) continue;"

Because our TTY logger's highest-set bit is LOG_FLAG_DEBUG, all info
events are processed, even though we've unset the LOG_FLAG_INFO event.

My proposed change configures lt_log: to examine whether a DDLogMessage's
specific LOG_FLAG_..* is set in loggerNode->logLevel.

[rivera-ernesto]

Related to #203.

Looks good to me.
Also we're getting to a point where DDlog.h/m files need a cleanup.

[matt-holden]

Fantastic.

I'm really loving working with this framework. I think I'll have to dig deeper into the codebase...

[matt-holden]

Thanks for pulling this in!

Do you happen to know when you plan to create the next .podspec?

[rivera-ernesto]

Should be soon, but in the mean time you can test it with the :head option.

[erlichmen]

@matt-holden thanks for the patch this fixes the need for a custom formatter that we needed to assign per logger.
BTW how do you setup the crash logger?

[rivera-ernesto]

In the case of Crashlytics there is already a logger available.

[bpoplauschi]

@matt-holden the new version (1.8.0) of Lumberjack is available.

[matt-holden]

Awesome!

Sent from my iPhone

On Jan 27, 2014, at 1:44 AM, Bogdan Poplauschi notifications@github.com wrote:

@matt-holden the new version (1.8.0) of Lumberjack is available.

—
Reply to this email directly or view it on GitHub.