[bug] MESSAGE_CONTENTS semantic convention not supported in Arize

[mshick]

Describe the bug
When sending spans to Arize via the openinference-vercel package, I noticed that message contents were not showing up in the span view nor in the attributes. They appear to be discarded. I traced the issue to the use of MESSAGE_CONTENTS here. I do not see message.contents available as a string or string list type in the Arize Semantic Conventions, so the use of the convention seems incorrect.

To Reproduce
Create an application using ai, @ai-sdk/openai, and @arizeai/openinference-vercel. Connect to an Arize (not Phoenix) service. Notice the lack of message contents when using the generateText method from ai.

Expected behavior
I would expect the message contents in the span provided by openinference-vercel to appear in Arize. Instead they appear to be discarded, perhaps because they are not known to the Arize semantic conventions?

Screenshots

Desktop (please complete the following information):
N/A

Additional context
We are currently running a custom fork of the package, where I concatenate and stringify the message.content array provided by ai and set it to the semantic convention llm.input_messages.N.message.content. These contents show up without issue in Arize.

[mikeldking]

Hey @mshick thanks for the issue! It probably is a instrumentation problem so will look into it. I mainly maintain phoenix however so please let me know if you would like support from the arize platform side as well!

[mikeldking]

Correction @mshick - it's actually an ingestion issue for muti-part messages on the Arize side. I've flagged the arize support team and they will help you out! It's tracked internally but let me know if you have any further questions.

[mshick]

Nice, thank you for looking into it. Can your team let me know when you've got it resolved so I can update / test on my end?

[mikeldking]

Hey @mshick I'm gonna tag a few engineers here just to track. @harrisonchu @nate-mar - the tracking issue is (https://github.com/Arize-ai/arize/issues/37154) (this is a private repo so only those that have access will be able to track).

I believe you wouldn't have this issue in Phoenix or even managed phoenix if you are willing to use that for now.