Uploaded image for project: 'Atlas Module'
  1. Atlas Module
  2. ATLAS-202

Clean up server logs

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Closed
    • Priority: TBD
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Complexity:
      Medium

      Description

      Atlas server logging could be improved. Currently, we are logging HTTP traffic (perhaps express is doing this), we have some debugging lines that didn't get cleaned up, we don't include timestamps, and we don't use a predictable format for logging.

      Atlas is listening at : http://localhost:3000
      connected
      GET / 200 57.193 ms - 7815
      GET /api/distributions 304 6.713 ms - -
      GET /api/types 304 8.769 ms - -
      GET /api/versions 304 10.913 ms - -
      GET /api/markers 200 8.104 ms - 2353
      GET /api/auth 200 4.202 ms - 651
      

      For IT administrators to support the server, we would ideally use a logging library (e.g., expand on our use of log4js) throughout the codebase so log entries at least have a timestamp (which can be incredibly helpful) and HTTP traffic has more standard/useful info (e.g., IP address of who requested).

        Gliffy Diagrams

          Attachments

            Activity

              People

              Assignee:
              heliostrike Sai Sandeep Mutyala
              Reporter:
              burke Burke Mamlin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: