Easier debugging with standardized logging

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Logging
    • Easier debugging with standardized logging
    • Java Drivers
    • None
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • 3
    • 1
    • 3
    • 100
    • 0
    • None
    • Hide

      Engineer(s): Ross Lawley, Slav Babanin
      2025-05-22: Target date set to 2025-05-19

      • What was accomplished since the last update?
        • Started phase 2 of finishing off this epic
        • JAVA-5697 Update SDAM spec to include error messages for electionId/setVersion mismatches - in code review
        • JAVA-5230 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor - in code review
        • JAVA-5229 Publish TopologyDescriptionChangedEvent on topology close - in progress, core work done but may require some larger unified test infrastructure changes to report the events.
      • What's the focus over the next two weeks?
        • Getting the above into main
        • Working on the remaining tickets
      • Any risks/blockers/impediments?
        • None expected.

      Engineer: Jeff

      Summary: Define a default set of debug logging messages that drivers should produce, and a standardized, trivial mechanism drivers should support for enabling, disabling, and configuring debug logging

      2023-01-20: Setting initial target end date to 2023-02-03

      • Logging and command monitoring spec changes in review
      • Supporting configurable max document length in command logging is up next
      Show
      Engineer(s): Ross Lawley, Slav Babanin 2025-05-22: Target date set to 2025-05-19 What was accomplished since the last update? Started phase 2 of finishing off this epic JAVA-5697 Update SDAM spec to include error messages for electionId/setVersion mismatches - in code review JAVA-5230 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor - in code review JAVA-5229 Publish TopologyDescriptionChangedEvent on topology close - in progress, core work done but may require some larger unified test infrastructure changes to report the events. What's the focus over the next two weeks? Getting the above into main Working on the remaining tickets Any risks/blockers/impediments? None expected. Engineer: Jeff Summary: Define a default set of debug logging messages that drivers should produce, and a standardized, trivial mechanism drivers should support for enabling, disabling, and configuring debug logging 2023-01-20: Setting initial target end date to 2023-02-03 Logging and command monitoring spec changes in review Supporting configurable max document length in command logging is up next
    • Hide

      DRIVERS-1204:

      • Implement logging infrastructure and unified test runners defined in DRIVERS-1677
      • Implement log messages and corresponding tests for each component
      Show
      DRIVERS-1204 : Implement logging infrastructure and unified test runners defined in DRIVERS-1677 Implement log messages and corresponding tests for each component

      This ticket was split from DRIVERS-1204, please see that ticket for a detailed description.

            Assignee:
            Ross Lawley
            Reporter:
            TPM Jira Automations Bot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              2 years, 9 weeks, 1 day