Traffic Server
  1. Traffic Server
  2. TS-55

Logging: Default settings for diagnostic logging

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.0a
    • Fix Version/s: 2.1.3
    • Component/s: Logging
    • Labels:
      None
    • Environment:

      All platforms

      Description

      Currently the default diagnostic logging settings are as follows in proxy/mgmt2/RecordsConfig.cc :

      1. O stdout
      2. E stderr
      3. S syslog
      4. L diags.log

      proxy.config.diags.output.diag E
      proxy.config.diags.output.debug E
      proxy.config.diags.output.status S
      proxy.config.diags.output.note S
      proxy.config.diags.output.warning S
      proxy.config.diags.output.error SE
      proxy.config.diags.output.fatal SE
      proxy.config.diags.output.alert SE
      proxy.config.diags.output.emergency SE

      This means regular diagnostics will be logged to syslogd. It has been suggested that syslog logging be disabled due to syslogd locking up the system under heavy load. Instead by default and all diagnostic output go to stderr(E) where the output can be captured by TrafficCop in 'traffic.out'. A new configuration could possibly look like this:

      proxy.config.diags.output.diag E
      proxy.config.diags.output.debug E
      proxy.config.diags.output.status E
      proxy.config.diags.output.note E
      proxy.config.diags.output.warning E
      proxy.config.diags.output.error E
      proxy.config.diags.output.fatal E
      proxy.config.diags.output.alert E
      proxy.config.diags.output.emergency E

      -George

        Activity

        Hide
        Leif Hedstrom added a comment -

        How about we leave "emergency" and "fatal" with SE, and the rest we change to "E" only. Thoughts?

        Show
        Leif Hedstrom added a comment - How about we leave "emergency" and "fatal" with SE, and the rest we change to "E" only. Thoughts?
        Hide
        Leif Hedstrom added a comment -

        George, what do you think? If you don't have time to look at this (and/or commit this), just let me know and I'll take this .

        Show
        Leif Hedstrom added a comment - George, what do you think? If you don't have time to look at this (and/or commit this), just let me know and I'll take this .
        Hide
        George Paul added a comment -

        Suggested changes look fine. I'll check it soon
        -G

        Show
        George Paul added a comment - Suggested changes look fine. I'll check it soon -G
        Hide
        George Paul added a comment -

        New defaults are

        proxy.config.diags.output.diag E
        proxy.config.diags.output.debug E
        proxy.config.diags.output.status E
        proxy.config.diags.output.note E
        proxy.config.diags.output.warning E
        proxy.config.diags.output.error SE
        proxy.config.diags.output.fatal SE
        proxy.config.diags.output.alert E
        proxy.config.diags.output.emergency SE

        Left error output going to syslog for deployments which monitor on syslogs

        Show
        George Paul added a comment - New defaults are proxy.config.diags.output.diag E proxy.config.diags.output.debug E proxy.config.diags.output.status E proxy.config.diags.output.note E proxy.config.diags.output.warning E proxy.config.diags.output.error SE proxy.config.diags.output.fatal SE proxy.config.diags.output.alert E proxy.config.diags.output.emergency SE Left error output going to syslog for deployments which monitor on syslogs

          People

          • Assignee:
            George Paul
            Reporter:
            George Paul
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development