Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-25024

Have the ability to mark the logs and roll them over for support reasons

XMLWordPrintable

      We need to the ability in the UI to mark the logs with a special message and also to cause a log rollover to happen.

      The driver behind this is better support.

        1. JRA-25024-500page-studio.txt
          31 kB

            [JRASERVER-25024] Have the ability to mark the logs and roll them over for support reasons

            ɹǝʞɐq pɐɹq added a comment -

            4.4.1

            ɹǝʞɐq pɐɹq added a comment - 4.4.1

            Andreas Knecht (Inactive) added a comment -

            Brad reckons this made it into 4.1.

            Andreas Knecht (Inactive) added a comment - Brad reckons this made it into 4.1.

            ɹǝʞɐq pɐɹq added a comment -

            For the record I intended that log mark to go into every log. I gather we could "micro optimise" to see if the http access log is on or not. The trick there is that there may be more tyhan one Logger that constitues "on"

            ɹǝʞɐq pɐɹq added a comment - For the record I intended that log mark to go into every log. I gather we could "micro optimise" to see if the http access log is on or not. The trick there is that there may be more tyhan one Logger that constitues "on"

            Trevor Campbell (Inactive) added a comment -

            QA Failed for 2 reasons.

            • MINOR - The Log mark is placed in all the logs and all the logs are rolled over even those that are disabled. E.g. The HttpAccessLog is marked and rolled even though HTTP Access Logging is not turned on. I'm not sure this is a bug, because there is no spec, so it is debatable, but it seems wrong to me.
            • MAJOR - Crahed on Studio. See attachment JRA-25024-500page-studio.txt. This is on JSODI Build Revision 160527.

            Trevor Campbell (Inactive) added a comment - QA Failed for 2 reasons. MINOR - The Log mark is placed in all the logs and all the logs are rolled over even those that are disabled. E.g. The HttpAccessLog is marked and rolled even though HTTP Access Logging is not turned on. I'm not sure this is a bug, because there is no spec, so it is debatable, but it seems wrong to me. MAJOR - Crahed on Studio. See attachment JRA-25024 -500page-studio.txt. This is on JSODI Build Revision 160527.

            ɹǝʞɐq pɐɹq added a comment -

            Yes with some effort. This required changes to core JIRA to enable all the loggers to partcipate and the appenders to allow rollover.

            Now that it is in JIRA, the STP could put a facade over it. Ideally the other applications could have the same behaviour and hence the STP could facade them all. But in the mean time I have made it part of the JIRA logging page.

            ɹǝʞɐq pɐɹq added a comment - Yes with some effort. This required changes to core JIRA to enable all the loggers to partcipate and the appenders to allow rollover. Now that it is in JIRA, the STP could put a facade over it. Ideally the other applications could have the same behaviour and hence the STP could facade them all. But in the mean time I have made it part of the JIRA logging page.

            sladey added a comment -

            brad, shouldn't this kind of thing be in the Support Tools plugin?

            sladey added a comment - brad, shouldn't this kind of thing be in the Support Tools plugin?

            ɹǝʞɐq pɐɹq added a comment -

            Its not really a bug but this allows it to go throught the QA process better on bugfix branch

            ɹǝʞɐq pɐɹq added a comment - Its not really a bug but this allows it to go throught the QA process better on bugfix branch

              bbaker ɹǝʞɐq pɐɹq
              bbaker ɹǝʞɐq pɐɹq
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: