Hi, I started implementing the new logging system, but came to a point where some design decisions are required by more experience people.
Main question is: *How is the logging supposed to work?* When running the current test-quite against my draft implementation, it raised a lot of errors. This made me rethink some behaviour which is currently tested by the test-suite: 1) Should messages go to stdout/stderr by default? IMHO messages should go to stdout or stderr *only* in two cases: a) While rading the config-file b) If the user runs the daemon with some "--verbose" option. 2) Should messages send via broks be terminated by '\n'? IMHO this is useless as it most probably will be stripped at the receiver anyway. (I did not check the source.) 3) Are level-names allowed to be upper-case? Or is there any program known to rely on these to be capitalized text? Currently they are capitalized, but the standard logging module uses upper-case names. If capitalized are required, we need to dig deeper into the code. 4) Should all messages (above the set level) be send to the broker, even e.g. those about reading the config file? 5) Do we need 'human format' for messages send as broks, too? -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible | ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
