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

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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

            Assignee:
            Allan BURDAJEWICZ
            Reporter:
            Oleg Nenashev
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: