|ReleasedLast Release||Jan 2018|
|LOCLines of Code||4,407|
CocoaLumberjack is a fast & simple, yet powerful & flexible logging framework for Mac and iOS.
If you installed using CocoaPods or manually:
DDLog.add(DDTTYLogger.sharedInstance) // TTY = Xcode console DDLog.add(DDASLLogger.sharedInstance) // ASL = Apple System Logs let fileLogger: DDFileLogger = DDFileLogger() // File Logger fileLogger.rollingFrequency = TimeInterval(60*60*24) // 24 hours fileLogger.logFileManager.maximumNumberOfLogFiles = 7 DDLog.add(fileLogger) ... DDLogVerbose("Verbose"); DDLogDebug("Debug"); DDLogInfo("Info"); DDLogWarn("Warn"); DDLogError("Error");
If you're using Lumberjack as a framework, you can
[DDLog addLogger:[DDTTYLogger sharedInstance]]; // TTY = Xcode console [DDLog addLogger:[DDASLLogger sharedInstance]]; // ASL = Apple System Logs DDFileLogger *fileLogger = [[DDFileLogger alloc] init]; // File Logger fileLogger.rollingFrequency = 60 * 60 * 24; // 24 hour rolling fileLogger.logFileManager.maximumNumberOfLogFiles = 7; [DDLog addLogger:fileLogger]; ... DDLogVerbose(@"Verbose"); DDLogDebug(@"Debug"); DDLogInfo(@"Info"); DDLogWarn(@"Warn"); DDLogError(@"Error");
It is similar in concept to other popular logging frameworks such as log4j, yet is designed specifically for Objective-C, and takes advantage of features such as multi-threading, grand central dispatch (if available), lockless atomic operations, and the dynamic nature of the Objective-C runtime.
In most cases it is an order of magnitude faster than NSLog.
It takes as little as a single line of code to configure lumberjack when your application launches. Then simply replace your NSLog statements with DDLog statements and that's about it. (And the DDLog macros have the exact same format and syntax as NSLog, so it's super easy.)
One log statement can be sent to multiple loggers, meaning you can log to a file and the console simultaneously. Want more? Create your own loggers (it's easy) and send your log statements over the network. Or to a database or distributed file system. The sky is the limit.
Configure your logging however you want. Change log levels per file (perfect for debugging). Change log levels per logger (verbose console, but concise log file). Change log levels per xcode configuration (verbose debug, but concise release). Have your log statements compiled out of the release build. Customize the number of log levels for your application. Add your own fine-grained logging. Dynamically change log levels during runtime. Choose how & when you want your log files to be rolled. Upload your log files to a central server. Compress archived log files to save disk space...
The current version of Lumberjack requires: