Quick Start
Tested Versions
HoneyHive’s Strands integration is tested against the following versions, as of April 2026. Newer patch releases are generally safe; pin to these versions to reproduce a known-good configuration.
Requires Python 3.11+.
Don’t use
openinference-instrumentation-strands-agents. That SpanProcessor (from Arize/OpenInference) isn’t supported by HoneyHive’s ingestion pipeline today and its spans may be dropped or misrouted. Strands’ native OTel path shown above is the recommended and fully supported approach.What Gets Traced
HoneyHive automatically captures:- Agent invocations - Every
agent()call with inputs and outputs - LLM calls - Model requests, responses, and token usage
- Tool executions - Each tool call with arguments and results
- Event loop cycles - Internal agent reasoning steps
Example: Agent with Tools
Example: AWS Bedrock Model Backend
Strands works with AWS Bedrock viaBedrockModel. You’ll need AWS credentials configured via any standard mechanism — ~/.aws/credentials, an IAM role, or environment variables:
Example: Multi-Agent (Agents-as-Tools)
Strands supports wrapping agents as tools for orchestration patterns:Adding Metadata
Session-Level (User Context)
Useenrich_session for metadata that applies to the entire session:
Span-Level (Agent Attributes)
Use Strands’ nativetrace_attributes for metadata on agent spans:
Troubleshooting
Traces not appearing
- Initialize HoneyHive first - Must be called before importing Strands:
-
Check environment variables - Ensure
HH_API_KEYis set - Verify model credentials - Ensure your model provider credentials are configured (Anthropic API key, AWS credentials, etc.)
Related
Enrich Your Traces
Add user IDs and custom metadata to Strands traces
Custom Spans
Create spans for business logic around agent calls
Distributed Tracing
Trace agents across service boundaries
Query Trace Data
Export traces programmatically

