Update Emitted Chat Spans to be compliant with OTEL gen_ai spec's changes
#83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update Emitted Chat Spans to be compliant with OTEL gen_ai spec's changes
Checklist
Type of Change
updating telemetry configuration
Summary of changes
Please refer to this to read about the reference
gen_aispec for OTEL.Updates:
xaiunder thegen_ai.provider.namefield instead of thegen_ai.systemfield.server.addressto beapi.x.ai. I'm not sure if it's to hard code it as the prod endpoint (i.e. what if we are testing the sdk locally/staging). I could alternatively plumb theapi_hostfield properly from the grpc channel creation forClientdown to the clients for each of the individual clients for chat, image, etc. but I'd like to get others' thoughts on this.Here is the reference documentation for OTEL
gen_aiI am using.