Compatible instrumentation
Halios works with standard OpenTelemetry-compatible traces and auto-instrumentors:Configure the OTLP exporter
Point your standard OpenTelemetry exporter to Halios using standard environment variables:GenAI semantics Halios understands
Halios recognizes common GenAI operations such as:- Model calls (input prompts, output completions, token usage)
- Tool execution (tool name, arguments, output results or errors)
- Retrieval (search queries, returned document chunks and IDs)
- Agent / Sub-agent delegation (multi-agent workflows, parent-child context)
gen_ai.operation.name, model/provider metadata, tool names, messages, usage, and related execution context.
Minimum recommended telemetry
For effective evaluations and debugging, aim to send:- One trace per agent interaction or run
- Parent-child span relationships preserved across async calls
- Model and tool operation names
- Tool arguments and results where available
- Input and output messages if evaluations inspect them
- Service and environment metadata (
service.name,deployment.environment.name,service.version)
Halios can ingest partial traces, but richer traces produce better debugging and evaluation data.
Redacting sensitive data
Trace payloads may contain prompts, user data, and tool arguments. Use your OpenTelemetry processor or exporter to redact or drop sensitive fields before export when required.Verify traces with the CLI
You can inspect and verify stored traces using the Halios CLI:CLI reference
Command reference for automation and CI pipelines.
Evaluation concepts
Core mental model and key evaluation terms.