Quick Start
The examples on this page useOpenAIChatCompletion, so they use OpenAIInstrumentor. If your Semantic Kernel app uses Anthropic, Bedrock, Gemini, or another provider, use the matching provider openinference instrumentor when one exists.
Last tested with
semantic-kernel 1.36.0 (May 2026).What Gets Traced
This integration uses dual-layer tracing. Semantic Kernel’s native OpenTelemetry diagnostics emit orchestration spans, while the provider instrumentor (e.g.OpenAIInstrumentor) adds detailed model payloads.
From SK-native diagnostics:
- Agent invocations -
ChatCompletionAgentcalls with agent name and instructions - Function / plugin calls - Each kernel function execution with arguments and results
- Multi-agent orchestration - Agents-as-plugins routing with triage and delegation structure
- LLM calls with full payloads - Chat messages, completions, tool calls, and token usage (requires
SEMANTICKERNEL_EXPERIMENTAL_GENAI_ENABLE_OTEL_DIAGNOSTICS_SENSITIVE)
Example: Agent with Plugin
Example: Multi-Agent (Agents-as-Plugins)
Semantic Kernel supports using agents as plugins for orchestration patterns:Troubleshooting
Traces not appearing
- Enable SK diagnostics first - Environment variables must be set before any imports:
-
Check environment variables - Ensure
HH_API_KEYis set -
Verify OpenAI credentials - Ensure
OPENAI_API_KEYis configured -
Instrument your provider - Use the matching provider instrumentor if you need model events with full inputs and outputs in HoneyHive. This page uses
OpenAIInstrumentorbecause the examples useOpenAIChatCompletion.
Missing prompts/completions in traces
Enable sensitive diagnostics and the matching provider instrumentor to capture full message content on model events. This OpenAI example usesOpenAIInstrumentor:
Related
Enrich Your Traces
Add user IDs and custom metadata to Semantic Kernel traces
Custom Spans
Create spans for business logic around agent calls
Distributed Tracing
Trace agents across service boundaries
Query Trace Data
Export traces programmatically

