OpenLLMetry

If your application is already instrumented with OpenLLMetry (Traceloop’s SDK), point its exporter at Rius and your existing traces flow in; no re-instrumentation needed.

Point the exporter here

from traceloop.sdk import Traceloop
 
Traceloop.init(
    app_name="my-agent",
    api_endpoint="https://ingest.eu.console.rius-glassflow.com",
    headers={"Authorization": "Bearer <your API key>"},
)

OpenLLMetry exports OTLP/HTTP protobuf by default, which is exactly what the endpoint expects. The same values can come from OpenLLMetry’s environment variables if you prefer configuration over code.

What gets captured

Traces arrive, spans nest, and prompt and completion content is visible in trace inspection. Attributes the platform normalizes are stored under their canonical keys, so search and filter on those, such as gen_ai.usage.input_tokens rather than gen_ai.usage.prompt_tokens.

OpenLLMetry has used several attribute conventions across versions, and the platform normalizes all of them at ingest onto the canonical keys: current releases already emit OTel GenAI (gen_ai.*) attributes; older ones flatten messages into gen_ai.prompt.* / gen_ai.completion.*, spell usage as gen_ai.usage.prompt_tokens / completion_tokens, and mark streaming as llm.is_streaming. The Traceloop decorators’ traceloop.span.kind (workflow, task, agent, tool) becomes the span taxonomy, the decorated function’s name becomes the tool or agent name, and traceloop.entity.input / output become the span’s input and output. Model, token, and cost analytics work across those versions; the mapping in full is in the supported-conventions matrix.

Two things are not mapped yet: the per-completion gen_ai.completion.N.finish_reason of older releases, and the flattened tool definitions under llm.request.functions.*. Both are stored under their own names.

For long agent runs on an older release, raise OpenTelemetry’s per-span attribute limit, since those releases record messages one attribute per field; see Attribute count limit.

Next steps

• Span attribute reference: which OpenLLMetry attribute families map to analytics today.
• OpenTelemetry Collector: fan out to Rius next to your existing backend while you evaluate.