Stop the log spam when the instance is locked

XMLWordPrintable

    • 0
    • 1

      In case an upgrade task fails, the instances goes into a locked state and shows an error message. That's good.

      But under the hood, Bamboo will log this locked state together with every incoming HTTP request into the server log. This quickly fills up the logs and in my case prevented me from revealing a problem because the logs with the important information were already rotated:

      @4000000054222e2520fed4ac 2014-09-24 02:36:11,553 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 12835kb
@4000000054222e2723a72ca4 2014-09-24 02:36:13,598 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e2723bd96ec 2014-09-24 02:36:13,599 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 11331kb
@4000000054222e292703ccf4 2014-09-24 02:36:15,654 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e29271d6f74 2014-09-24 02:36:15,656 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 9852kb
@4000000054222e2b2a081414 2014-09-24 02:36:17,704 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e2b2a540964 2014-09-24 02:36:17,706 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 8353kb
@4000000054222e2d2d5fde1c 2014-09-24 02:36:19,761 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e2d2d775dbc 2014-09-24 02:36:19,762 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 16060kb
@4000000054222e2f30a9dce4 2014-09-24 02:36:21,816 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e2f30c9c4dc 2014-09-24 02:36:21,818 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 14574kb
@4000000054222e3133773d54 2014-09-24 02:36:23,863 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e31338efb74 2014-09-24 02:36:23,864 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 13085kb
@4000000054222e333669775c 2014-09-24 02:36:25,912 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e3336b2a9a4 2014-09-24 02:36:25,914 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 11597kb
@4000000054222e35395aa3dc 2014-09-24 02:36:27,962 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e3539773844 2014-09-24 02:36:27,964 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 10104kb
@4000000054222e3801839c84 2014-09-24 02:36:30,025 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e38019d1fc4 2014-09-24 02:36:30,027 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 8624kb
@4000000054222e3a05582fdc 2014-09-24 02:36:32,089 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e3a0570c8bc 2014-09-24 02:36:32,090 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 16385kb
@4000000054222e3c0856e534 2014-09-24 02:36:34,139 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e3c086ed61c 2014-09-24 02:36:34,141 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 14888kb
@4000000054222e3e0b26e584 2014-09-24 02:36:36,187 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e3e0b3fa574 2014-09-24 02:36:36,188 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 13380kb
@4000000054222e400e5d7b8c 2014-09-24 02:36:38,240 INFO [TP-Processor2] [JohnsonFilter] The application is still starting up, or there are errors.  Redirecting request from '/rest/api/latest/info' to '/error/errorEvents.action'
@4000000054222e400ee485dc 2014-09-24 02:36:38,246 INFO [TP-Processor2] [AccessLogFilter] 59.167.29.201 GET https://sbac-acceptor-it32-3.jira-dev.com/builds/error/errorEvents.action 11917kb

      Instead I suggest to only log the output of the JohnsonFilter once and not on every request.

      Ideally, the default (OnDemand) configuration should not do any access logging and if so do it into a separate log file which can have a different log rotation rule applied.

            Assignee:
            Unassigned
            Reporter:
            Martin Meinhold
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: