Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-3694

Document named logging

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • v1.3.14, mongodb-3.0
    • Affects Version/s: None
    • Component/s: manual
    • Labels:
      None

      SERVER-5092 introduced log components for finer-grained control over output of LOG() messages.
      These log components will be extended into a hierarchy namespace in SERVER-14415 and will be configured using setParameter (BSON support to be added in SERVER-14416)

      • Add logComponentVerbosity to the list of server parameters in setParameter
      • Every log component will have a corresponding YAML configuration option with the name systemLog.component.<component dotted name>.verbosity. Dotted name of each log component includes names ancestor components up to but not include the Default component. For complete list, see LogComponent::Value enumeration in src/mongo/logger/log_component.h. Currently, the complete list of YAML options for log components is:
        • systemLog.component.accessControl.verbosity
        • systemLog.component.commands.verbosity
        • systemLog.component.indexing.verbosity
        • systemLog.component.networking.verbosity
        • systemLog.component.query.verbosity
        • systemLog.component.replication.verbosity
        • systemLog.component.sharding.verbosity
        • systemLog.component.storage.verbosity
        • systemLog.component.storage.journaling.verbosity
        • systemLog.component.writes.verbosity
        • systemLog.component.geo.verbosity
        • systemLog.component.control.verbosity
      • Server Logging Rules will need to incorporate the information from the logging section of the updated Kernel Code Style:

            Assignee:
            kay.kim@mongodb.com Kay Kim (Inactive)
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              9 years, 19 weeks, 2 days ago