[ENH] return chroma-trace-id header, include trace ID in thrown errors

[codetheweb]

Returns a new chroma-trace-id header for both successful and errored responses.

Tested locally with Jaeger.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[HammadB]

Should we follow this convention?

https://www.w3.org/TR/trace-context/

[HammadB]

Thanks! We can always munge to standards later if we want, I linked that for reference.

[codetheweb]

Should we follow this convention?

w3.org/TR/trace-context

interesting, it seems like this is focused on forwarding trace context upstream rather than returning it downstream though

[HammadB]

Yep, if we wanted to make the client the originator we could use this

…

On Wed, Jul 24, 2024 at 11:35 AM Max Isom ***@***.***> wrote: Should we follow this convention? w3.org/TR/trace-context <https://www.w3.org/TR/trace-context/> interesting, it seems like this is focused on forwarding trace context upstream rather than returning it downstream though — Reply to this email directly, view it on GitHub <#2570 (comment)>, or unsubscribe <https:/notifications/unsubscribe-auth/ABKW32JF7BMIN7MMY7UTXPTZN7XWJAVCNFSM6AAAAABLM5FVIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBYGY3DMNZXGY> . You are receiving this because you commented.Message ID: ***@***.***>