Arize AI Community Icon

Home
Events

Arize AX Releases
Arize AX Support
Arize News
Arize Observe
Discussions
Introductions
Phoenix Support

Powered by Tightknit

Phoenix Support

Phoenix Support

Debugging Undefined Not Valid JSON Error in Spans

·Jan 02, 2025 08:13 PM

Hi, we're seeing this "undefined" is not valid JSON error for some spans, and I'm not sure how to debug it.

9 comments

· Sorted by Oldest

RunLLM
APP
·
It seems likely that the error you're encountering is related to the handling of JSON data within the Phoenix platform. My understanding is that this could be due to improper serialization or deserialization of data, as seen in issues like this one where span_kind was not serializable by pyarrow. Additionally, there might be issues with parsing invocation parameters, as noted in this issue, where errors are not properly surfaced, leading to lossy information.Would you like more details on how to address this issue or any specific aspect of Phoenix? Sources: - GitHub Issue 2437 - this issue
💡 Hint: Mention RunLLM in the thread for followups.
Rusty
·
We are using llama-index, and this error seems to occur only for Anthropic achat calls with function calling.
Rusty
·
I'm trying to debug a bunch of spans where an anthropic model failed to properly call a function, and this error seems to correlate with that as well.
Roger Y.
·
if you click the “Attributes” tab, what does it look like? do you see “undefined” anywhere?
Rusty
·
I don't see "undefined" on that tab, no. It's a lot of content there. I prefer not to share the whole of it here, but if it's helpful I could DM it to you.
Roger Y.
·
yea, you can DM me if you like
👍🏻1
✔️1
Rusty
·
Currently:
FROM arizephoenix/phoenix:version-7.0.1
:thankyou:1
Rusty
·
Thanks for taking the time to dig into this and fix it! 🙏🏻
:np:1
Rusty
·
Confirmed fixed 🙌🏻
❤️1