Add diagnostic metadata to identify retried commands

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      One of client backpressure's goals is to add metrics around successfully retried commands. To do that we need to introduce a new field so that clients can tag retried commands (perhaps "retry": 1...2...3). The client fields will be added in DRIVERS-3241.

      We may also want to attach other metadata like the backoff & jitter durations (DRIVERS-3239), and client retry budget (DRIVERS-3240).

            Assignee:
            Unassigned
            Reporter:
            Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: