Problem
When Relay projects a mark as an OpenInference TOOL span, the canonical payload is available only through Relay-specific JSON-string attributes such as nemo_relay.mark.data_json and nemo_relay.mark.metadata_json. OpenInference consumers such as Phoenix therefore cannot present the mark through their standard tool output and metadata views without downstream normalization.
The plugins already emit structured Relay mark data correctly, and ATOF/ATIF preserve it. This gap belongs in the OpenInference exporter rather than each plugin.
Proposed behavior
For TOOL-projected marks, add the standard OpenInference tool name, JSON output, MIME type, and metadata attributes while retaining all existing nemo_relay.mark.* attributes for compatibility and lossless round-tripping.
Generic OTEL and native mark-event behavior should remain unchanged.
Problem
When Relay projects a mark as an OpenInference TOOL span, the canonical payload is available only through Relay-specific JSON-string attributes such as
nemo_relay.mark.data_jsonandnemo_relay.mark.metadata_json. OpenInference consumers such as Phoenix therefore cannot present the mark through their standard tool output and metadata views without downstream normalization.The plugins already emit structured Relay mark data correctly, and ATOF/ATIF preserve it. This gap belongs in the OpenInference exporter rather than each plugin.
Proposed behavior
For TOOL-projected marks, add the standard OpenInference tool name, JSON output, MIME type, and metadata attributes while retaining all existing
nemo_relay.mark.*attributes for compatibility and lossless round-tripping.Generic OTEL and native mark-event behavior should remain unchanged.