class
Logger extends AnyRef
Instance Constructors
-
new
Logger(name: String, dispatcher: EntryDispatcher)
Value Members
-
final
def
!=(arg0: AnyRef): Boolean
-
final
def
!=(arg0: Any): Boolean
-
final
def
##(): Int
-
final
def
==(arg0: AnyRef): Boolean
-
final
def
==(arg0: Any): Boolean
-
final
def
asInstanceOf[T0]: T0
-
def
buildEntry(level: Level, message: Message, tags: Set[Tag]): Entry
-
def
clone(): AnyRef
-
-
final
def
eq(arg0: AnyRef): Boolean
-
def
equals(arg0: Any): Boolean
-
def
finalize(): Unit
-
final
def
getClass(): Class[_]
-
def
hashCode(): Int
-
final
def
isInstanceOf[T0]: Boolean
-
def
log(level: Level, tag: Tag*)(message: Message): Unit
-
def
log(level: Level, message: Message, tag: Tag*): Unit
-
def
log(level: Level, message: Message): Unit
-
def
log(level: Level, message: Message, tags: Set[Tag]): Unit
-
val
name: String
-
final
def
ne(arg0: AnyRef): Boolean
-
final
def
notify(): Unit
-
final
def
notifyAll(): Unit
-
final
def
synchronized[T0](arg0: ⇒ T0): T0
-
def
toString(): String
-
final
def
wait(): Unit
-
final
def
wait(arg0: Long, arg1: Int): Unit
-
final
def
wait(arg0: Long): Unit
Inherited from AnyRef
Inherited from Any
The main application interface into timber.
Loggers are what applications use to inject @link Entries into the system.
Loggers don't support the isEnabled type methods provided by some other logging systems. That's because the Logger doesn't make any decisions regarding where (or if) the entry it creates is actually written into a log file or processed in any way.
The idea behind timber is that the application thread gets to return to what it's doing as quickly as possible.
Arguably, this is better for the application code because your application code shouldn't be dependent on the logging configuration. You have to try really hard to write code that depends on logging configuration.