CocoaLumberjack is a fast & simple, yet powerful & flexible logging framework for Mac and iOS.
- install via CocoaPods
platform :ios, '5.0'
pod 'CocoaLumberjack'
- or install manually
- read the Getting started guide, check out the FAQ section or the other docs
- if you find issues or want to suggest improvements, create an issue or a pull request
- for all kinds of questions involving CocoaLumberjack, use the Google group or StackOverflow (use #lumberjack).
- Replace
DDLog.h
imports by#import <CocoaLumberjack/CocoaLumberjack.h>
. - Replace all
DDLogC
macros for regularDDLog
macros. - Replace any
ddLogLevel
variable's type toDDLogLevel
- Replace log level (
LOG_LEVEL_*
) macros withDDLogLevel
enum values - Replace log flag (
LOG_FLAG_*
) macros withDDLogFlag
enum values - Replace
DDLogMessage
ivars and method calls to the new ivars and methodslogMsg
with_message
logLevel
with_level
logFlag
with_flag
logContext
with_context
lineNumber
with_line
(type changed fromint
toNSUInteger
)file
with_file
(filename
contains just the file name, without the extension and the full path)timestamp
with_timestamp
methodName
withfunction
- Replace
DDAbstractLogger
formatter
tologFormatter
YSSingleFileLogger
ivars are no longer accesible, use the methods instead- Replace
[DDLog addLogger:withLogLevel:]
with[DDLog addLogger:withLevel:]
If an included library requires it, you can force CocoaLumberjack 1.x by setting the version before the conflicting library:
pod 'CocoaLumberjack', '~> 1.9'
pod 'ConflictingLibrary'
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...
- You're looking for a way to track down that impossible-to-reproduce bug that keeps popping up in the field.
- You're frustrated with the super short console log on the iPhone.
- You're looking to take your application to the next level in terms of support and stability.
- You're looking for an enterprise level logging solution for your application (Mac or iPhone).
- Get started using Lumberjack
- Different log levels for Debug and Release builds
- Different log levels for each logger
- Use colors in the Xcode debugging console
- Write your own custom formatters
- FAQ
- Analysis of performance with benchmarks
- Common issues you may encounter and their solutions
- AppCode support
- Full Lumberjack documentation
- Xcode 4.4 or later is required
- iOS 5 or later
- OS X 10.7 or later
- for OS X < 10.7 support, use the 1.6.0 version
- Robbie Hanson
- Love the project? Wanna buy me a coffee? (or a beer :D)
- CocoaLumberjack is available under the BSD license. See the LICENSE file.