LlamaIndex

Trace LlamaIndex pipelines with Rius: query engines, retrievers, embeddings, and the model calls inside them.

Setup

pip install "glassflow-rius[llama-index]" llama-index

The extra installs the instrumentation, not llama-index itself, so the package is named here for a fresh environment. A project that already calls LlamaIndex has it, and pip leaves it untouched. Without it, init() logs a DependencyConflict and this integration stays off.

import rius
 
rius.init(api_key="gf_...", service_name="my-agent")
# build indexes and query engines exactly as before

What gets captured

A query becomes a nested trace of typed spans: retrieval steps as RETRIEVER spans, embedding calls as EMBEDDING, synthesis model calls as LLM spans with model, token usage, and messages (cost computed server-side). RAG debugging usually starts here: the retriever span’s output shows what the model was given to work with.

Verify

Run one query against an index, then open the trace in the console: the pipeline appears as nested spans with the LLM leaf carrying model, tokens, and cost.