[JIRA] (JENKINS-39595) UX: Prevent setting performance-killer configurations in custom system log Web UIs

2 views
Skip to first unread message

o.v.nenashev@gmail.com (JIRA)

unread,
Nov 8, 2016, 1:39:01 PM11/8/16
to jenkinsc...@googlegroups.com
Oleg Nenashev created an issue
 
Jenkins / Improvement JENKINS-39595
UX: Prevent setting performance-killer configurations in custom system log Web UIs
Issue Type: Improvement Improvement
Assignee: Unassigned
Components: core
Created: 2016/Nov/08 6:38 PM
Labels: ux logging
Priority: Major Major
Reporter: Oleg Nenashev

When a Jenkins admin creates a new custom system log in the Web UI, he gets a Web form with "Level.ALL" logging level and empty Logger specification. If the admin occasionally saves the configuration, it leads to logging of ALL log entries in the system.

Such behavior easily kills large Jenkins instances. In order to avoid it, we need:

  • Form validation and warning in the case of such setting
  • Ideally: Additional confirmation page to ensure the admin knows what he is doing
  • Nice2Have: Administrative monitor for such custom logger settings
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

jglick@cloudbees.com (JIRA)

unread,
Nov 8, 2016, 2:26:01 PM11/8/16
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Nov 8, 2016, 2:28:01 PM11/8/16
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue

Would also be wise for SupportLogFormatter to cap the total number of messages it will log in a given time period to some reasonable value, just in case a single logger is too verbose.

Change By: Jesse Glick
Component/s: support-core-plugin

aburdajewicz@cloudbees.com (JIRA)

unread,
Aug 18, 2019, 7:39:02 PM8/18/19
to jenkinsc...@googlegroups.com
Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ
Change By: Allan BURDAJEWICZ
Assignee: Allan BURDAJEWICZ
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages