1. glassfish
  2. GLASSFISH-3466

messages in log files should put important info first


    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 9.1pe
    • Fix Version/s: not determined
    • Component/s: logging
    • Labels:
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:


      Filing report as suggested by Kedar in

      I request a user-friendlier default log format, and/or a simple way to configure
      the format of the lines written to server.log.

      For example:
      to check connection: Connection refused:

      My text editor does not wrap this, so I cannot see the actual message unless I
      scroll to the right.

      I'd like to see the most important fields first:
      1. timestamp (to prevent me from looking at old messages)
      2. level (many INFO messages are written and I only want to check if
      there were no big problems)
      3. the message itself

      Depending on the message I might be interested in the thread info (only
      with threading issues I suppose, or to compare the RequestID with
      entries in other logs?), or the component (for debugging GF?), but only
      AFTER I checked the message.

      I understand the product version string is included for Sun's support team.
      Please put it last.

      Also, most fields only note their value, but the thread field also seems
      to include labels (_ThreadID, _ThreadName and _RequestID) cluttering up
      the line even more. Why?
      If they are always written in the same order, why not drop the labels?
      We can figure out which value starts and ends where from the separators
      (';') between them...


        No work has yet been logged on this issue.


          • Assignee:
            Dies Koper
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: