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

Investigate changes in SERVER-46843: Structured Logging does not log in ISO-8601 Section 5.6 format

    XMLWordPrintable

    Details

      Description

      Description

      Downstream Change Summary

      Time zone offset now contains a colon between hours and minutes per https://tools.ietf.org/html/rfc3339#section-5.6

      Description of Linked Ticket

      I was running structured logs through the Java Driver and I think the timestamp format we’re currently using is incorrect, specifically for timezone offsets, according to the Extended JSON Spec. On 4.3.4 I’m getting timestamps like "2020-03-12T17:38:02.344-0400" which does not include a : in the offset -0400 however the extended JSON spec calls out specifically that it only supports timezones in the ISO-8601 “Internet Date/Time Format” which corresponds to section 5.6 of RFC-3339 where the only valid time-numoffset includes a :.

      This ticket should track a solution that allows drivers following the extended JSON spec to parse structured logs as extended JSON objects according to spec. That might take the form of changing the timestamp string's format, adjusting the extended JSON spec, or another solution I can't see.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              andrew.feierabend Andrew Feierabend (Inactive)
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Backlog - Core Eng Program Management Team Backlog - Core Eng Program Management Team
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 21 weeks ago
                Date of 1st Reply: