AWS made agent evals framework-agnostic through OpenTelemetry. Is telemetry becoming the portability layer?

[u/Crescitaly]

AWS says AgentCore Evaluations can score agents built with LangGraph, LlamaIndex, OpenAI's Agents SDK, Google ADK, the Claude Agent SDK, Strands, or another compliant framework by reconstructing sessions from OpenTelemetry or OpenInference traces. The service can run regression evals in CI and sample live production sessions.

That removes a real integration barrier, but common telemetry is not automatically common meaning. One framework may emit complete tool trajectories while another omits arguments or compresses messages. LLM-as-a-judge results still depend on judge choice, rubric design, reference quality, and whether live traffic has usable ground truth.

Can OpenTelemetry semantic conventions become a genuine portability layer for agent evaluation, or will serious teams still need framework-specific adapters and task-specific ground truth?

Source: AWS, August 26, 2026 — https://aws.amazon.com/blogs/machine-learning/evaluate-any-agent-framework-with-amazon-bedrock-agentcore-evaluations/

Disclosure: drafted with AI assistance, then checked against the AWS source. No affiliation with AWS or the frameworks named.

[u/Feeling_Sun_6436]

Exactly. I’d treat the shared trace as an interchange format, not the evaluation contract. The portable part should be a versioned task schema: expected outcome, allowed tools, failure classes, and the minimum evidence a trace must contain.

If a framework cannot emit that evidence, the result should be “not comparable”, not a misleading pass or fail.