Update SpanTelemetryContextImpl usage of baggage

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • 2
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we use the OTEL provided baggage for keeping a reference of the keepSpan value. We are wasting resources by needing to update the baggage for each span created. We could fix by only setting it on the baggage on egress, and reading from the baggage on ingress, and keep a reference to it as a member variable or some other means.

            Assignee:
            Unassigned
            Reporter:
            Ben Gawel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: