v0.1.15
Identity propagation for multi-agent orchestrators
Services that host multiple logical agents (e.g. a demo portal or orchestration layer) can now declare themselves as an orchestrator via service_role="orchestrator" in traccia.init(). This prevents the host service's service.name from being registered as a standalone agent on the Traccia platform. The declaration is propagated automatically to both the trace and metrics OTLP resources.
Per-run agent identity on all metric data points
All framework instrumentations — OpenAI, Anthropic, LangChain, OpenAI Agents SDK, and CrewAI — now stamp the per-run agent_id, agent_name, and environment (from runtime_config.run_identity) directly onto OTLP metric data point attributes. This ensures that token usage, cost, and latency metrics are attributed to the correct logical agent in multi-agent setups, rather than falling back to the process-level service.name.
CrewAI instrumentation improvements
- Agent identity from run_identity is now correctly propagated to agent-level and LLM-level metric data points emitted during CrewAI crew execution.
- Fixed an overly broad guard condition in _attach_run_identity that could suppress identity stamping in certain edge cases.