4 // Fraunhofer Institute for Open Communication Systems (FOKUS)
5 // Competence Center NETwork research (NET), St. Augustin, GERMANY
6 // Stefan Bund <g0dil@berlios.de>
8 // This program is free software; you can redistribute it and/or modify
9 // it under the terms of the GNU General Public License as published by
10 // the Free Software Foundation; either version 2 of the License, or
11 // (at your option) any later version.
13 // This program is distributed in the hope that it will be useful,
14 // but WITHOUT ANY WARRANTY; without even the implied warranty of
15 // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16 // GNU General Public License for more details.
18 // You should have received a copy of the GNU General Public License
19 // along with this program; if not, write to the
20 // Free Software Foundation, Inc.,
21 // 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
23 /** \mainpage The SENF Logging library
25 The Loggger infrastructure implements a highly flexible compile- and run-time configurable
26 logging infrastructure supporting multiple streams, user definable log areas and fine grained
27 log levels. Logging can be configured at compile and runtime on any combination of above
28 parameters. The library supports a host of log targets and messages can be routed into multiple
29 targets at the same time. To allow concise usage of the library, a utility to define logging
30 defaults for any scope is provided.
38 \section logging_concepts Concepts
40 Log messages are arbitrarily created throughout the code using simple log statements (which are
41 macros). Besides the log message itself, every log message is labeled with additional
42 information: The \e stream, the \e area and a log \e level. If the message is not compile-time
43 disabled, the message is then directed to one or several log \e targets.
45 A \e stream combines log messages with a single purpose: Debug messages, access logging and so
46 on. Any number of streams may be defined. There is one predefined default stream called \c
47 senf::log::Debug. (see: \ref SENF_LOG_DEF_STREAM)
49 The \e area gives information about the source location of the message. Areas may be defined and
50 assigned arbitrarily but should be used to label messages from a single class or subsystem. It
51 is possible to reuse a class as it's own area tag, which is often desireable. There is a
52 default area \c senf::log::DefaultArea which is used, when no other area is assigned. (see: \ref
53 SENF_LOG_DEF_AREA, \ref SENF_LOG_CLASS_AREA)
55 The log \e level gives information on the importance of the message. The list of log-levels is
56 fixed. (see: \ref loglevels)
58 Depending on their the \e stream, \e area and \e level information, log messages can be enabled
59 or disabled at \e compile time. Messages disabled at compile time should not generate any
60 code. (see: \ref SENF_LOG_CONF)
62 To be of any use, the log messages have to be written somewhere. This is the responsibility of
63 any number of \e targets. A \e target receives messages and using it's routing information
64 decides, wether the message is output or not. A message may be routed to multiple targets
65 simultaneously or may not be output by any target at all. (see: \ref targets)
67 \section logging_tutorial Tutorial introduction
69 Using the logging library mostly concerns using \ref SENF_LOG statements in your code. There are
70 some other helpers used to simplify specifying parameters.
75 // Define a new log stream with default level, runtime limit and compile time limit
76 // set to senf::log::MESSAGE
77 SENF_LOG_DEF_STREAM( UserLog, senf::log::MESSAGE, senf::log::MESSAGE, senf::log::MESSAGE );
81 // Define a log area which will automatically be used by all members of this class.
82 // This is a combination of SENF_LOG_DEF_AREA and SENF_LOG_DEFAULT_AREA.
83 SENF_LOG_CLASS_AREA();
85 // Set default log parameters for this scope.
86 SENF_LOG_DEFAULT_STREAM(foo::UserLog);
87 SENF_LOG_DEFAULT_LEVEL(senf::log::NOTICE);
89 // Define an alias for emergency debug messages
90 // The log area is inherited from the default at the place, where this
91 // alias is used *not* where it is defined
92 SENF_LOG_DEF_ALIAS(LogEmerg, (senf::log::Debug)(senf::log::CRITICAL));
101 void foo::Froblizer::froblize()
103 SENF_LOG(("This is the UserLog at level NOTICE in the FroblizeArea"));
104 SENF_LOG((senf::log::WARNING) ("Same stream and area but at warning level"));
105 SENF_LOG((LogEmerg) ("This goes to the DebugLog at level CRITICAL in the FroblizerArea"));
108 void foo::Froblizer::test()
110 // Change the default log level for this method. stream and area are taken
111 // from the next scope up
112 SENF_LOG_DEFAULT_LEVEL(senf::log::VERBOSE);
114 SENF_LOG(("Log to UserLog stream in Froblizer area however at VERBOSE level"));
117 int main(int, char **)
119 // Set up the routing targets
120 senf::log::ConsoleTarget & console (senf::log::ConsoleTarget::instance());
121 senf::log::FileTarget logfile ("my.log");
123 // Debug messages go to the console
124 console.route<senf::log::Debug>();
125 // Important user message are written to the log file
126 logfile.route<foo::UserLog, senf::log::IMPORTANT>();
130 \implementation I would have much preferred a more C++ like implementation. However given the
132 \li Flexible configuration at compile and runtime
133 \li Concise usage and simple interface
134 \li Zero overhead for compile-time disabled log messages
136 I did not find any non-mcaro implementation which was not either completely convoluted,
137 unusable or slow. So I turned to a macro based implementation which can provide all the
138 design goals stated above.
145 // comment-column: 40
146 // c-file-style: "senf"
147 // indent-tabs-mode: nil
148 // ispell-local-dictionary: "american"
149 // compile-command: "scons -u test"