Fiddler Strands SDK
Native monitoring for Strands Agents with Strands Agents SDK
Monitor Strands Agent applications with Fiddler's purpose-built SDK. The Strands Agents SDK provides deep visibility into agent reasoning, tool execution, and multi-agent coordination for Strands-based agent applications.
Platform Compatibility: Works with Strands agents deployed on any platform, including AWS Bedrock, custom infrastructure, or other cloud providers.
What You'll Need
Fiddler account (cloud or on-premises)
Strands agent application
Python 3.10 or higher
Fiddler API key
Quick Start
# Step 1: Install (uv recommended)
uv add fiddler-strands
# or: pip install fiddler-strands# Step 2: Set up telemetry and instrumentation
import os
from strands.telemetry import StrandsTelemetry
from fiddler_strandsagents import StrandsAgentInstrumentor
strands_telemetry = StrandsTelemetry()
strands_telemetry.setup_otlp_exporter() # Sends to Fiddler
StrandsAgentInstrumentor(strands_telemetry).instrument()
# Step 3: Create your Strands agent as usual
from strands import Agent
from strands.models.openai import OpenAIModel
model = OpenAIModel(api_key=os.getenv("OPENAI_API_KEY"))
agent = Agent(model=model, system_prompt="You are a helpful assistant")
# Step 4: Agent calls are automatically traced
response = agent("Hello, how are you?")Prerequisites: Configure OpenTelemetry environment variables for Fiddler integration:
What Gets Monitored
Strands Agent Operations
Agent Invocations - Full request/response capture with timing
Tool Execution - Tool and API call tracking
Knowledge Base Queries - RAG retrieval and context usage
Prompt Orchestration - Prompt templates and LLM interactions
Session Management - Multi-turn conversation tracking
Strands-Specific Metrics
Reasoning Traces - Agent thought process and decision-making
Tool Execution - Success rates, latency, error patterns
Knowledge Retrieval - Relevance scores, source attribution
Multi-Agent Coordination - Cross-agent communication patterns
Infrastructure Metrics - Platform-specific infrastructure calls
Configuration Options
Environment Variables (OpenTelemetry Standard)
The SDK uses standard OpenTelemetry environment variables for configuration:
See the Quick Start Guide for detailed configuration steps.
Programmatic Configuration
Example Applications
Customer Service Agent with Tools
Multi-Agent System
Viewing Your Data
Navigate to Fiddler UI to analyze Strands Agent performance:
Agent Overview - Overall agent performance metrics
Session Analysis - Multi-turn conversation flows
Action Group Metrics - Tool usage patterns and success rates
Knowledge Base Performance - Retrieval quality and relevance
Cost Tracking - Token usage and AWS costs per agent
Key Metrics
Agent Latency: P50/P95/P99 response times
Tool Success Rate: Percentage of successful action group executions
Retrieval Quality: Knowledge base query relevance scores
Token Usage: LLM tokens consumed per session
Error Rates: Failed invocations by error type
Advanced Features
Custom Metadata with Helper Functions
The SDK provides helper functions to enrich your traces with custom business context:
Conversation Tracking
Session-Level Attributes
Span-Level Attributes
LLM Context
Troubleshooting
Traces Not Appearing in Fiddler
Verify environment variables:
Check instrumentation is enabled:
Test with console exporter:
Missing Agent Attributes on Child Spans
Verify SDK instrumentation:
Add custom attributes:
Performance Optimization
The SDK uses batch span processing by default for minimal overhead. For additional optimization:
Disable console exporter in production:
Adjust batch processor settings:
Related Documentation
Strands Agents SDK Quick Start - Detailed setup guide
Fiddler Evals SDK - Evaluate Strands Agent quality
Strands Agents SDK Reference - Complete class and method documentation
Last updated
Was this helpful?