Open mkovatsc opened 10 years ago
The first thing to do would be to migrate to SLF4J API. We can then better integrate into existing environments by means of letting the user decide which logging framework to use (there are bindings for almost all existing frameworks available).
Furthermore, SLF4J's API supports the use of Marker
s that can be used to label log messages and use these labels for filtering (given that the underlying logging framework supports Markers). This way operational logging could be achieved by means of adding a particular Marker, e.g. operational
when logging a message. In the logging configuration the user can then decide what to log and at what level.
How to do logging and how to improve it? There are two types of logging for Californium:
To improve this concept, it would be great to know if there are other things that are interesting during operation.
In the long-run, we might also want to change the internal logger. Maybe we can align the logger implementation over multiple IoT Eclipse projects or at least find something that is good for all Californium committers.