[SSSD] RFC: Improving the debug messages

Jakub Hrozek jhrozek at redhat.com
Tue Jun 30 10:04:09 UTC 2015


On Tue, Jun 30, 2015 at 10:30:16AM +0200, Jan Pazdziora wrote:
> > - Running sssd in environment where all actions complete successfully
> >   should emit no debug messages. Default log level should be moved to
> >   SSSDBG_OP_FAILURE or CRIT_FAILURE. (This basically amounts to checking
> >   all OP, FATAL and CRIT failure messages..)
> > 
> >   The reason is that sometimes sssd fails, but because logging is
> >   totally silent, we don't know what happened at all. Currently we have
> >   a couple of small bugs where we might print a loud DEBUG message just
> >   because we search for an entry which is not there etc.
> 
> It'd be great if the default option was to emit one error message per
> failure (per operation, where operation should be defined from user's
> point of view, not developer's point of view) and no message for
> success. The next level would be to have one error message per failure
> and one message per success, so that it's easy to observe what is
> going on without getting into too much detail.

What someone (sorry, I already forgot who :-/) also suggested during a
discussion was to add a new log level for start and end of an operation.



More information about the sssd-devel mailing list