Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39595

UX: Prevent setting performance-killer configurations in custom system log Web UIs

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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

        Attachments

          Activity

          Hide
          jglick Jesse Glick added a comment -

          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.

          Show
          jglick Jesse Glick added a comment - 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.

            People

            • Assignee:
              Unassigned
              Reporter:
              oleg_nenashev Oleg Nenashev
            • Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: