[JIRA] (JENKINS-42235) Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning

2017-02-21 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-42235  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning   
 

  
 
 
 
 

 
 Should probably just discard root loggers with ALL/FINEST/FINER/FINE level, or force their level to a higher (i.e. less verbose) one.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42235) Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning

2017-02-21 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42235  
 
 
  Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2017/Feb/21 9:17 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Owen Mehegan  
 

  
 
 
 
 

 
 As I learned the hard way, the Jenkins log recorder UI makes it easy for you to accidentally create an unfiltered recorder with a log level of 'ALL' (because that is the default level), and this will easily overwhelm and take down Jenkins if it is under normal load. In my case the only way to recover was to find the log recorder config XML file on the filesystem, move it aside, and restart Jenkins. This caused an unpleasant 25 minute production outage for us. I would propose that if the user attempts to create an empty recorder at level ALL we should throw a warning dialog, explaining that this configuration can be dangerous, and give them the option to back out. Alternatively, maybe the default level should be SEVERE rather than ALL, so that if you accidentally create an unfiltered recorder it won't log much. Daniel Beck you want to comment on this? I can make an attempt at implementation if you think the logic is sound.  
 

  
 
 
 
 

 
 
 

 
 
 Add 

[JIRA] (JENKINS-42235) Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning

2017-02-21 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42235  
 
 
  Attempting to create a root/unfiltered log recorder with level 'ALL' should display a warning   
 

  
 
 
 
 

 
Change By: 
 Owen Mehegan  
 

  
 
 
 
 

 
 As I learned the hard way, the Jenkins log recorder UI makes it easy for you to accidentally create an unfiltered recorder with a log level of 'ALL' (because that is the default level), and this will easily overwhelm and take down Jenkins if it is under normal load. In my case the only way to recover was to find the log recorder config XML file on the filesystem, move it aside, and restart Jenkins. This caused an unpleasant 25 minute production outage for us.I would propose that if the user attempts to create an empty recorder at level ALL we should throw a warning dialog, explaining that this configuration can be dangerous, and give them the option to back out.Alternatively, maybe the default level should be SEVERE rather than ALL, so that if you accidentally create an unfiltered recorder it won't log much.[~danielbeck]  do  you want to comment on this? I can make an attempt at implementation if you think the logic is sound.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)