feat(otlp): Parse JSON-looking attributes in span attributes panel

[gggritso]

Until EAP supports array storage, we are storing array attributes as JSON-encoded strings. Since we can't know all array attribute names ahead of time, scan through the attributes and look for any value that seems like it'll be a JSON array, and render it using the JSON renderer if appropriate.

Closes OPE-51.

e.g.,

[linear]

OPE-51 Render array values nicely in Trace Item Attributes

[gggritso]

@ArthurKnaus most of the AI semantic attributes fall under this category, but I'm not confident which ones and when. If you like, it'd be good to remove any known array attributes from the JSON_ATTRIBUTES list.

[cursor]

Bug: Custom Renderers Overwritten by Truncation Loop

The TRUNCATED_TEXT_ATTRIBUTES loop unconditionally overwrites custom renderers, unlike the dynamic JSON detection which checks for existing renderers. This results in attributes that are both auto-detected as JSON arrays and listed in TRUNCATED_TEXT_ATTRIBUTES being incorrectly rendered as truncated text instead of parsed JSON.

static/app/views/performance/newTraceDetails/traceDrawer/details/span/eapSections/attributes.tsx#L200-L211

sentry/static/app/views/performance/newTraceDetails/traceDrawer/details/span/eapSections/attributes.tsx

Lines 200 to 211 in 1afea82

	// array values, so SDKs often store array values as JSON-encoded strings.
	sortedAndFilteredAttributes.forEach(attribute => {
	if (Object.hasOwn(customRenderers, attribute.name)) return;
	if (attribute.type !== 'str') return;
	if (!looksLikeAJSONArray(attribute.value)) return;
	customRenderers[attribute.name] = jsonRenderer;
	});
	for (const attribute of TRUNCATED_TEXT_ATTRIBUTES) {
	customRenderers[attribute] = truncatedTextRenderer;
	}

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎

[Abdkhan14]

This makes sense to me, we custom render the string value as an array, and should be able to search by the string value in explore (through cell actions). We keep assuming that everything in trace-item -> attributes is searchable in explore.