Configures OTEL-based tracing for LLM apps using TruLens. Assists in setting up, debugging, and optimizing AI workflows.
Install
mkdir -p .claude/skills/trulens-instrumentation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2331" && unzip -o skill.zip -d .claude/skills/trulens-instrumentation && rm skill.zipInstalls to .claude/skills/trulens-instrumentation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Instrument LLM apps with TruLens OTEL-based tracing - from setup to debugging and optimizationKey capabilities
- →Auto-instrument LangChain, LangGraph, and LlamaIndex
- →Add custom spans with @instrument decorator
- →Capture user inputs and model outputs
- →Map function arguments to trace attributes
- →Instrument third-party classes
How it works
It uses framework wrappers or decorators to inject OTEL-based tracing spans into the application execution flow for visualization and evaluation.
Inputs & outputs
When to use trulens-instrumentation
- →Add tracing to LLM pipeline
- →Debug LLM evaluation metrics
- →Optimize model performance with TruLens
About this skill
TruLens Instrumentation
Instrument your LLM application to capture traces for evaluation and debugging. This skill covers everything from initial setup to iterative improvement of trace quality.
When to Use This Skill
- Setting up instrumentation for a new app
- Adding custom spans to framework-wrapped apps
- Improving trace readability (unclear span names, missing context)
- Debugging why evaluations aren't working (missing attributes)
- Optimizing what gets captured for visualization
Part 1: Setup
Instrument your LLM application to capture traces for evaluation and debugging.
Interactive Instrumentation Setup
Let's identify what you need to instrument for visualization and/or evaluation.
Question 1: What framework are you using?
| Framework | Wrapper | Auto-instrumented |
|---|---|---|
| LangChain | TruChain | Chain components, LLM calls |
| LangGraph | TruGraph | Graph nodes, @task decorators |
| LlamaIndex | TruLlama / TruLlamaWorkflow | Query engines, retrievers, workflows |
| Custom/Other | TruApp | Only what you explicitly @instrument() |
→ If using a framework, the wrapper handles basic instrumentation automatically. Continue to Question 2 to add custom attributes.
Question 2: What data do you want to capture?
Tell me what's important to track in your app. This could be for:
- Visualization: Understanding execution flow in the dashboard
- Evaluation: Feeding data into feedback functions
Common attributes to instrument:
| What to Capture | Span Type | Attributes |
|---|---|---|
| User query/input | RECORD_ROOT | INPUT |
| Final response | RECORD_ROOT | OUTPUT |
| Retrieved documents/chunks | RETRIEVAL | QUERY_TEXT, RETRIEVED_CONTEXTS |
| LLM prompts/completions | GENERATION | (auto-captured by wrappers) |
| Tool calls | TOOL | Tool name, arguments, results |
| Agent reasoning | AGENT | Plans, decisions |
| Reranking results | RERANKING | QUERY_TEXT, INPUT_CONTEXT_TEXTS, TOP_N |
What specific data do you want to capture that isn't listed above?
Examples:
- "I want to capture the similarity scores from my retriever"
- "I need to track which documents were filtered out"
- "I want to see the intermediate chain-of-thought reasoning"
- "I need to capture metadata about each retrieved chunk (source, page number)"
Question 3: Do you have custom functions that need instrumentation?
If you have functions that aren't automatically instrumented, list them:
Example response:
retrieve_documents(query)- returns list of documentsrerank_results(query, docs)- reranks and filters documentsgenerate_response(query, context)- calls LLM to generate answer
For each function, I'll help you add the right @instrument() decorator with appropriate span types and attributes.
Template: Instrumenting Your Custom Function
Tell me about your function and I'll generate the instrumentation:
Function name: _______________
What it does: _______________
Input parameters: _______________
What it returns: _______________
What data should be captured for eval/visualization: _______________
Example:
Function name: retrieve_documents
What it does: Searches vector store for relevant documents
Input parameters: query (str), top_k (int)
What it returns: List of document dicts with 'text', 'source', 'score' keys
What data should be captured: The query text and the document texts (not scores/sources)
→ Generated instrumentation:
@instrument(
span_type=SpanAttributes.SpanType.RETRIEVAL,
attributes={
SpanAttributes.RETRIEVAL.QUERY_TEXT: "query",
SpanAttributes.RETRIEVAL.RETRIEVED_CONTEXTS: "return",
}
)
def retrieve_documents(query: str, top_k: int = 5) -> list:
# If you need to extract just the text from complex returns:
pass
# Or with lambda for complex extraction:
@instrument(
span_type=SpanAttributes.SpanType.RETRIEVAL,
attributes=lambda ret, exception, *args, **kwargs: {
SpanAttributes.RETRIEVAL.QUERY_TEXT: kwargs.get("query", args[0]),
SpanAttributes.RETRIEVAL.RETRIEVED_CONTEXTS: [doc["text"] for doc in ret],
}
)
def retrieve_documents(query: str, top_k: int = 5) -> list:
pass
Overview
TruLens provides two approaches to instrumentation:
- Framework Wrappers: Auto-instrument apps built with LangChain, LangGraph, or LlamaIndex
- Custom Instrumentation: Use
@instrument()decorator for custom apps or to add additional spans to framework apps
Prerequisites
pip install trulens
# For framework-specific support:
pip install trulens-apps-langchain # LangChain/LangGraph
pip install trulens-apps-llamaindex # LlamaIndex
Instructions
Step 1: Initialize TruSession
from trulens.core import TruSession
session = TruSession()
Step 2: Choose Your Instrumentation Approach
Option A: Framework Wrappers (Recommended for Framework Apps)
For LangChain apps:
from trulens.apps.langchain import TruChain
tru_recorder = TruChain(
chain,
app_name="MyLangChainApp",
app_version="v1"
)
with tru_recorder as recording:
result = chain.invoke("your query")
For LangGraph apps:
from trulens.apps.langgraph import TruGraph
# TruGraph auto-detects graph nodes and @task decorators
tru_recorder = TruGraph(
graph,
app_name="MyLangGraphAgent",
app_version="v1"
)
with tru_recorder as recording:
result = graph.invoke({"messages": [HumanMessage(content="your query")]})
Deep Agents / LangGraph Instrumentation
LangChain's Deep Agents framework is built on LangGraph. Use TruGraph for full instrumentation:
from deepagents import create_deep_agent
from trulens.apps.langgraph import TruGraph
from trulens.core import TruSession
# Create the Deep Agent
agent = create_deep_agent(
model=model,
tools=[your_tools],
system_prompt="Your prompt"
)
# Wrap with TruGraph - captures all internal nodes, tool calls, planning steps
tru_agent = TruGraph(
agent,
app_name="DeepAgent",
app_version="v1",
feedbacks=[f_answer_relevance]
)
with tru_agent as recording:
result = agent.invoke({"messages": [{"role": "user", "content": query}]})
For LlamaIndex apps
from trulens.apps.llamaindex import TruLlama
tru_recorder = TruLlama(query_engine, app_name="MyRAG", app_version="v1")
with tru_recorder as recording:
result = query_engine.query("your query")
**For LlamaIndex query engines:**
```python
from trulens.apps.llamaindex import TruLlama
query_engine = index.as_query_engine()
tru_recorder = TruLlama(
query_engine,
app_name="MyLlamaIndexApp",
app_version="v1"
)
with tru_recorder as recording:
result = query_engine.query("your query")
For LlamaIndex workflows:
from trulens.apps.llamaindex import TruLlamaWorkflow
tru_recorder = TruLlamaWorkflow(
workflow,
app_name="MyLlamaWorkflow",
app_version="v1"
)
with tru_recorder as recording:
result = await workflow.run(query="your query")
Option B: Custom Instrumentation with @instrument()
For custom apps or to add spans to framework apps:
from trulens.apps.app import TruApp
from trulens.core.otel.instrument import instrument
from trulens.otel.semconv.trace import SpanAttributes
class MyRAG:
@instrument(
span_type=SpanAttributes.SpanType.RETRIEVAL,
attributes={
SpanAttributes.RETRIEVAL.QUERY_TEXT: "query",
SpanAttributes.RETRIEVAL.RETRIEVED_CONTEXTS: "return",
},
)
def retrieve(self, query: str) -> list:
# Your retrieval logic
return contexts
@instrument(span_type=SpanAttributes.SpanType.GENERATION)
def generate(self, query: str, contexts: list) -> str:
# Your generation logic
return response
@instrument(
span_type=SpanAttributes.SpanType.RECORD_ROOT,
attributes={
SpanAttributes.RECORD_ROOT.INPUT: "query",
SpanAttributes.RECORD_ROOT.OUTPUT: "return",
},
)
def query(self, query: str) -> str:
contexts = self.retrieve(query)
return self.generate(query, contexts)
rag = MyRAG()
tru_app = TruApp(rag, app_name="MyCustomRAG", app_version="v1")
with tru_app as recording:
result = rag.query("your query")
Step 3: Combining Wrappers with Custom Instrumentation
Use @instrument() alongside framework wrappers to add custom span attributes for evaluation:
from trulens.apps.langgraph import TruGraph
from trulens.core.otel.instrument import instrument
from trulens.otel.semconv.trace import SpanAttributes
@instrument()
def preprocess_input(topic: str) -> str:
"""Custom preprocessing - will appear in traces."""
return f"Preprocessed: {topic}"
@instrument(
span_type=SpanAttributes.SpanType.RETRIEVAL,
attributes={
SpanAttributes.RETRIEVAL.QUERY_TEXT: "query",
SpanAttributes.RETRIEVAL.RETRIEVED_CONTEXTS: "return",
},
)
def custom_retrieve(query: str) -> list:
"""Custom retrieval with semantic attributes for evaluation."""
return ["context1", "context2"]
# TruGraph will capture both auto-instrumented spans and your @instrument spans
tru_recorder = TruGraph(graph, app_name="EnhancedAgent", app_version="v1")
Step 4: Lambda-Based Attribute Extraction
For complex data structures, use a lambda to extract attributes:
@instrument(
span_type=SpanAttributes.SpanType.RETRIEVAL,
attributes=lambda ret, exception, *args, **kwargs: {
SpanAttributes.RETRIEVAL.RETRIEVED_CONTEXTS: [doc["text"] for doc in ret],
SpanAttributes.RETRIEVAL.QUERY_TEXT: kwargs.get("query", args[0] if args else ""),
}
)
def retrieve_documents(query: str) -> list:
return [{"
---
*Content truncated.*
When not to use it
- →Instrumenting non-LLM applications
Prerequisites
Limitations
- →Requires root span to be RECORD_ROOT for evaluation shortcuts
- →Manual instrumentation needed for non-framework code
How it compares
It provides specific framework-aware wrappers that automatically handle span creation, unlike generic manual instrumentation.
Compared to similar skills
trulens-instrumentation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| trulens-instrumentation (this skill) | 2 | 3mo | Review | Intermediate |
| langfuse | 7 | 6mo | No flags | Intermediate |
| langsmith-observability | 4 | 7mo | Review | Intermediate |
| mlops-observability | 2 | 6mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by truera
View all by truera →You might also like
langfuse
davila7
Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production. Use when: langfuse, llm observability, llm tracing, prompt management, llm evaluation.
langsmith-observability
davila7
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
mlops-observability
fmind
Guide to implement full stack observability including reproducibility, lineage, monitoring, alerting, and explainability.
distributed-tracing
wshobson
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
phoenix-observability
davila7
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
mlflow
davila7
Track ML experiments, manage model registry with versioning, deploy models to production, and reproduce experiments with MLflow - framework-agnostic ML lifecycle platform