Replace connection numeric ident with app services co_id in log prefix when possible

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      Log messages for sync connections currently look like

      Realm.Sync.Client.Session - Connection[1] Session[1]: Binding '/var/folders/s3/rtk055q91y15yg1hg2c373w40000gp/T/realm_xMukli/realm.ujjPaV' to ''
      Realm.Sync.Client.Session - Connection[1] Session[1]: Activating
      Realm.Sync.Client.Session - Connection[1] Session[1]: client_reset_config = false, Realm exists = true
      Realm.Sync.Client.Session - Connection[1] Session[1]: client_file_ident = 0, client_file_ident_salt = 0
      Realm.Sync.Client.Session - Connection[1] Session[1]: last_version_available  = 6
      Realm.Sync.Client.Session - Connection[1] Session[1]: progress_download_server_version = 0
      Realm.Sync.Client.Session - Connection[1] Session[1]: progress_download_client_version = 0
      Realm.Sync.Client.Session - Connection[1] Session[1]: progress_upload_server_version = 0
      Realm.Sync.Client.Session - Connection[1] Session[1]: progress_upload_client_version = 0
      Realm.Sync.Client.Session - Connection[1] Connecting to 'ws://localhost:9090/api/client/v2.0/app/basic_flx_connect-vwiolyg/realm-sync'
      

      Where the "Connection[1]" is a counter of the number of connections created by the sync client. While we do log the co_id when connected, it would be helpful if the log prefix contained the coi_id for every log message so it's easy to correlate events back to the server logs.

              Assignee:
              Jonathan Reams
              Reporter:
              Jonathan Reams
              Archiver:
              Marc Greenfield

                Created:
                Updated:
                Resolved:
                Archived: