Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-80150

Log negotiated network compressor with client metadata

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0, 7.0.6, 5.0.25, 6.0.14
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • Fully Compatible
    • v7.0, v6.0, v5.0, v4.4
    • Service Arch 2023-09-18, Service Arch 2023-10-02

      To better identify if network compression is being used by client applications via the drivers it would be helpful to have successful compressor negotiation messages logged ad the default log level.

      Unable to find source-code formatter for language: noformat. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
      {"t":{"$date":"2023-08-16T13:28:06.636-04:00"},"s":"D3","c":"NETWORK","id":22937,"ctx":"conn12","msg":"supported compressor","attr":{"compressor":"zlib"}}
      

      When the MessageCompressorManager logs a successful negotiation it is at D3 verbosity, which won't be printed to mongos/mongod logs.

            Assignee:
            james.bronsted@mongodb.com James Bronsted
            Reporter:
            alex.bevilacqua@mongodb.com Alex Bevilacqua
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: