Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2353

AMQ on Openshift: no date and time stamps in broker log file

    Details

    • Target Release:
    • Workaround Description:
      Hide

      Using S2I one can probably configure a custom broker logging config

      Show
      Using S2I one can probably configure a custom broker logging config
    • Release Notes Text:
      Hide
      Cause: No timestamps in default broker log configuration
      Consequence: Difficult to decipher logs
      Fix: Added a script that configures the broker log configuration file to include timestamps before every log message in the format: yyyy-mm-dd hh:mm:ss
      Result: Logs are easier to interpret
      Show
      Cause: No timestamps in default broker log configuration Consequence: Difficult to decipher logs Fix: Added a script that configures the broker log configuration file to include timestamps before every log message in the format: yyyy-mm-dd hh:mm:ss Result: Logs are easier to interpret
    • Sprint:
      CLOUD Maintenance Sprint 20

      Description

      The broker log of a broker running on OpenShift does not contain and date and time stamp information.
      For production environments this is a must!

      The default broker images should use a broker logging config that also logs date and time stamp.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  kliberti Kyle Liberti
                  Reporter:
                  mielket Torsten Mielke
                  Tester:
                  Marek Schmidt
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  9 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: