OpenTelemetry Quick Start
Monitor custom AI agents and multi-framework agentic applications with Fiddler using OpenTelemetry's native instrumentation.
What You'll Learn
In this guide, you'll learn how to:
Set up OpenTelemetry tracing for custom agent frameworks
Configure Fiddler as your OTLP endpoint with proper authentication
Map agent attributes to Fiddler's semantic conventions
Create instrumented LLM and tool spans with required attributes
Verify traces in the Fiddler dashboard
Time to complete: ~10-15 minutes
Prerequisites
Before you begin, ensure you have:
Fiddler Account: An active account with a GenAI application created
Python 3.10+
OpenTelemetry Packages:
pip install opentelemetry-api opentelemetry-sdk opentelemetry-exporter-otlp-proto-http
LLM Provider (for examples): OpenAI API key or similar
Fiddler Access Token: Get your token from Settings > Credentials
Create Fiddler Application
Log in to your Fiddler instance and navigate to GenAI Apps
Select "Add Application" to create a new application
Copy your Application ID - This must be a valid UUID4 format (e.g.,
550e8400-e29b-41d4-a716-446655440000)Get your Access Token from Settings > Credentials
Important: Keep your Application ID and Access Token secure. You'll need both for the next steps.
Configure Environment Variables
Set up your environment to connect to Fiddler's OTLP endpoint:
Environment Variable Breakdown:
OTEL_EXPORTER_OTLP_ENDPOINT
Your Fiddler instance URL
https://org.fiddler.ai
OTEL_EXPORTER_OTLP_HEADERS
Authentication and app ID headers
authorization=Bearer sk-...,fiddler-application-id=550e8400...
OTEL_RESOURCE_ATTRIBUTES
Resource-level application identifier
application.id=550e8400-e29b-41d4-a716-446655440000
Python Configuration (alternative to environment variables):
Tip: Store credentials in a .env file and use python-dotenv for local development:
Instrument Your Agent
Create instrumented spans for your agent's operations. Fiddler requires specific attributes to properly categorize and visualize your agent traces.
Required Fiddler Attributes
Resource Level (set via environment variable):
application.id- UUID4 of your Fiddler application
Trace Level (required in all spans):
gen_ai.agent.name- Name of your AI agentgen_ai.agent.id- Unique identifier for the agent
Span Level (required for each span):
fiddler.span.type- Type of operation:"chain","tool","llm", or"other"
Example: Simplified Travel Agent
Key Implementation Details:
Chain Spans: Use
fiddler.span.type = "chain"for high-level workflowsLLM Spans: Include model, system prompt, user input, output, and token usage
Tool Spans: Include tool name, input JSON, and output JSON
Nested Spans: Create parent-child relationships to show execution flow
Verify Monitoring
Run your instrumented code using the example above
Wait 1-2 minutes for traces to appear in Fiddler
Navigate to GenAI Apps in your Fiddler instance
Verify application status changes to Active
View traces to see your agent spans, hierarchy, and attributes
Success Criteria:
✅ Application shows as Active in GenAI Apps ✅ Traces appear with correct agent name ✅ Span hierarchy shows chain → LLM → tools relationship ✅ All required attributes are present (agent name, agent ID, span type) ✅ LLM token usage is tracked ✅ Tool inputs and outputs are captured
Verification Tip: Check the trace timeline view to see the execution flow of your agent, including which tools were called and how long each operation took.
Attribute Reference
Required Attributes
Resource Level:
application.id
string
UUID4 of your Fiddler application
"550e8400-e29b-41d4-a716-446655440000"
Trace Level (all spans):
gen_ai.agent.name
string
Name of the AI agent
"travel_agent"
gen_ai.agent.id
string
Unique identifier for the agent
"travel_agent_v1"
Span Level:
fiddler.span.type
string
Type of operation
"chain", "tool", "llm", "other"
Optional Attributes
Conversation Tracking:
gen_ai.conversation.id
string
Session/conversation identifier
"conv_123"
LLM Span Attributes:
gen_ai.request.model
string
Model name
"gpt-4o-mini", "claude-3-opus"
gen_ai.system
string
LLM provider
"openai", "anthropic"
gen_ai.llm.input.system
string
System prompt
"You are a helpful assistant"
gen_ai.llm.input.user
string
User input
"What's the weather?"
gen_ai.llm.output
string
LLM response
"The weather is sunny"
gen_ai.usage.input_tokens
int
Input tokens used
42
gen_ai.usage.output_tokens
int
Output tokens used
28
gen_ai.usage.total_tokens
int
Total tokens used
70
Tool Span Attributes:
gen_ai.tool.name
string
Tool/function name
"search_database"
gen_ai.tool.input
string
Tool input (JSON)
"{\"query\": \"hotels\"}"
gen_ai.tool.output
string
Tool output (JSON)
"{\"results\": [...]}"
Custom User-Defined Attributes:
fiddler.session.user.{key}
Trace (all spans)
fiddler.session.user.user_id = "usr_123"
fiddler.span.user.{key}
Span (individual)
fiddler.span.user.department = "sales"
Troubleshooting
Common Issues
Problem: Application not showing as "Active"
Solutions:
Verify environment variables are set correctly
Check that
OTEL_EXPORTER_OTLP_ENDPOINTincludes your Fiddler instance URLEnsure
OTEL_EXPORTER_OTLP_HEADERScontains valid authorization token and application IDAdd console exporter to verify spans are being generated locally
Check network connectivity:
curl -I https://your-instance.fiddler.ai
Problem: ModuleNotFoundError for OpenTelemetry packages
Solutions:
Problem: Spans not appearing in Fiddler
Solutions:
Verify required attributes are set:
Check resource attributes:
Enable console exporter for debugging:
Problem: Authentication errors (401 Unauthorized)
Solutions:
Regenerate your access token from Fiddler Settings > Credentials
Verify header format:
authorization=Bearer <token>,fiddler-application-id=<uuid>Ensure no extra spaces in header values
Check token hasn't expired
Problem: Invalid Application ID error
Solutions:
Copy Application ID directly from Fiddler UI
Verify UUID4 format:
550e8400-e29b-41d4-a716-446655440000Ensure no extra quotes or whitespace
Configuration Options
Basic Configuration
Advanced Configuration
High-Volume Applications (Batch Processing Tuning):
Environment Variable Configuration:
Sampling for Production (Reduce Volume):
Compression (Reduce Network Usage):
Using FiddlerClient Alternative (Simplified Setup):
Next Steps
Now that you have OpenTelemetry integration working:
Advanced Patterns: Download the Advanced OpenTelemetry Notebook for:
Multi-agent configurations
Conversation tracking across sessions
Custom user-defined attributes
Production-ready error handling
Comprehensive debugging techniques
Consider SDKs for Common Frameworks:
Fiddler LangGraph SDK - Auto-instrumentation for LangGraph/LangChain
Strands Agents SDK - Native Strands agent integration
Explore Fiddler Capabilities:
Production Deployment:
Review sampling strategies for cost optimization
Implement error handling and retry logic
Set up monitoring alerts
Configure custom attributes for your business context