BIND 10 #555: C++ Logging - multiple destinations and configuration

[BIND 10 Development]

#555: C++ Logging - multiple destinations and configuration
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  stephen                            |                Status:  reviewing
                       Type:         |             Milestone:
  enhancement                        |  Sprint-20110614
                   Priority:  major  |            Resolution:
                  Component:         |             Sensitive:  0
  logging                            |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  8.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by stephen):

 * owner:  stephen => vorner


Comment:

 > But maybe it's better than kill the whole server ...
 I think so - better a degraded service than no service at all.

 > ...admins should have something to parse the logs for them and email
 them or so.
 In production environments, sysadmins usually have monitoring packages
 (such as [http://www.nagios.org Nagios]) that warn them of trouble.

 > I didn't mean the name of the logger, I meant the filename of the
 replacement dictionary...
 I've updated the header comments of LoggerManager::init() (in
 logger_manager.h) to reflect that.

 > Anyway, do we need the impldef.{h,cc} files in git?
 For the present, yes.  The files are created by the message compiler,
 which depends on the logging code, which in turn depends on these files.
 A longer-term goal could be to separate the files related to messages and
 the files related to logging and build the message-related code first.  In
 that case, by the time the files are needed the message compiler would be
 built and they could be generated from the .mes file. But that is for
 another ticket.

-- 
Ticket URL: <http://bind10.isc.org/ticket/555#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development