[bind10-dev] Python logging framework proposal

[zhanglikun]

> I cannot really evaluate what we need here, but this seems overly
> complicated.  I'd be surprised if we have more than:
> 
>   logger = ISC::Logger.create("application-or-context-name")
>   logger.error "error message here"
>   logger.warn "warning here"
>   logger.info "info message here"
>   logger.debug "debug message here"
> 
> and so on.  Why would we need any more flexibility in how logging is
> handled?

I read somewhere that bind9's logsys is sexy, so maybe we plan to make
bind10's logsys more sexy. I like log level can be configured in runtime
very much.

> Before we solve the problem, I think we need to define just what logging
> is.  I know it seems obvious, but "trace this packet and report all
> activity around it" is one form of logging, but is likely out of scope
> for what we generally think of as "logging."
> 
> Along with logging, alerting is often important.  This is where bind 9
> fails; we are very good at reporting things to syslog, but we are really
> bad at any sort of "scoreboard" type of alarm status or error reporting
> that can be polled.  Do we want to combine these or not?  I would say
> not right now, but "is my server healthy?" is a question we should be
> able to answer without requiring someone to look through log files.

Yeah, agree,
How about the alerting is done by stats module? like, If stats find there
are 10 error or warning logs in 1 minutes, ok, the server isn't healthy now,
send one alert email to administrator to report it.


Zhang Likun