[JENKINS-18959] /log/all polluted with FINE* messages from other loggers #14781

Activity

1. jenkins-infra-bot commented on Jul 26, 2013

   

   jenkins-infra-bot

   on Jul 26, 2013

   Author

   More actions

   scm_issue_link:

   • Original comment link
   • Raw content of original comment:

     Code changed in jenkins
     User: Jesse Glick
     Path:
      changelog.html
      core/src/main/java/hudson/WebAppMain.java
     http://jenkins-ci.org/commit/jenkins/010d9e9067b7fa3ce776ec5f76a6cc4d0fdff258
     Log:
       [FIXED JENKINS-18959] /log/all should not show FINE messages from custom loggers.
     
     
     
     

   Code changed in jenkins
   User: Jesse Glick
   Path:
   changelog.html
   core/src/main/java/hudson/WebAppMain.java
   http://jenkins-ci.org/commit/jenkins/010d9e9067b7fa3ce776ec5f76a6cc4d0fdff258
   Log:
   [FIXED JENKINS-18959] /log/all should not show FINE messages from custom loggers.
2. jenkins-infra-bot

   closed this as completedon Jul 26, 2013
3. jenkins-infra-bot commented on Jul 26, 2013

   

   jenkins-infra-bot

   on Jul 26, 2013

   Author

   More actions

   dogfood:

   • Original comment link
   • Raw content of original comment:

     Integrated in  jenkins_main_trunk #2751
          [FIXED JENKINS-18959] /log/all should not show FINE messages from custom loggers. (Revision 010d9e9067b7fa3ce776ec5f76a6cc4d0fdff258)
     
          Result = SUCCESS
     Jesse Glick : 010d9e9067b7fa3ce776ec5f76a6cc4d0fdff258
     Files : 
     
     	
     changelog.html
     	
     core/src/main/java/hudson/WebAppMain.java
     
     
     

   Integrated in jenkins_main_trunk #2751
   [FIXED JENKINS-18959] /log/all should not show FINE messages from custom loggers. (Revision 010d9e9)

   Result = SUCCESS
   Jesse Glick : 010d9e9067b7fa3ce776ec5f76a6cc4d0fdff258
   Files :

   • changelog.html
   • core/src/main/java/hudson/WebAppMain.java
4. jenkins-infra-bot commented on Jul 30, 2013

   

   jenkins-infra-bot

   on Jul 30, 2013

   Author

   More actions

   jameshowe:

   • Original comment link
   • Raw content of original comment:

     It's less confusing for /log/all not to show all logs?
     

   It's less confusing for /log/all not to show all logs?
5. jenkins-infra-bot commented on Jul 30, 2013

   

   jenkins-infra-bot

   on Jul 30, 2013

   Author

   More actions

   jglick:

   • Original comment link
   • Raw content of original comment:

     Well /log/all never shows all log records; by default it always shows everything logged at INFO and above (after a fix I made a few months ago to not restrict it to hudson.* and jenkins.* namespaces); but then it was also showing FINE and lower records that were only being logged at all because other /log/* loggers had been configured to show them. This is because in java.util.logging, to receive log records you need to both set the level of the logger low enough and attach a handler to it, but these are separate acts: all handlers attached to the logger will receive the same records.
     
     So this fix tries to avoid sending the finer log records to all when they are already being displayed somewhere else, currently just by limiting all to INFO and above. It probably needs some adjustment since you can also—IMHO quite confusingly—adjust levels of arbitrary loggers in the Jenkins UI without adding a /log/* logger.
     

   Well /log/all never shows all log records; by default it always shows everything logged at INFO and above (after a fix I made a few months ago to not restrict it to hudson.* and jenkins.* namespaces); but then it was also showing FINE and lower records that were only being logged at all because other /log/* loggers had been configured to show them. This is because in java.util.logging, to receive log records you need to both set the level of the logger low enough and attach a handler to it, but these are separate acts: all handlers attached to the logger will receive the same records.

   So this fix tries to avoid sending the finer log records to all when they are already being displayed somewhere else, currently just by limiting all to INFO and above. It probably needs some adjustment since you can also—IMHO quite confusingly—adjust levels of arbitrary loggers in the Jenkins UI without adding a /log/* logger.
6. jenkins-infra-bot commented on Sep 17, 2013

   

   jenkins-infra-bot

   on Sep 17, 2013

   Author

   More actions

   scm_issue_link:

   • Original comment link
   • Raw content of original comment:

     Code changed in jenkins
     User: Jesse Glick
     Path:
      changelog.html
      core/src/main/java/hudson/WebAppMain.java
     http://jenkins-ci.org/commit/jenkins/8a45a9946caf132727b210a7d1786159e4a1d079
     Log:
       [FIXED JENKINS-18959] /log/all should not show FINE messages from custom loggers.
     (cherry picked from commit 010d9e9067b7fa3ce776ec5f76a6cc4d0fdff258)
     
     
     

   Code changed in jenkins
   User: Jesse Glick
   Path:
   changelog.html
   core/src/main/java/hudson/WebAppMain.java
   http://jenkins-ci.org/commit/jenkins/8a45a9946caf132727b210a7d1786159e4a1d079
   Log:
   [FIXED JENKINS-18959] /log/all should not show FINE messages from custom loggers.
   (cherry picked from commit 010d9e9)
7. jenkins-infra-bot

   added

   bugFor changelog: Minor bug. Will be listed after featuresFor changelog: Minor bug. Will be listed after features

   imported-jira-issue

   component:core

   priority:major

   resolution:fixed

   on Nov 24, 2025
8. jenkins-infra-bot

   added the

   Bug

   issue type on Nov 25, 2025
9. jenkins-infra-bot

   removed

   bugFor changelog: Minor bug. Will be listed after featuresFor changelog: Minor bug. Will be listed after features

   on Nov 25, 2025