New to Scorecard? Head straight to the Tracing Quickstart or jump into our ready-to-run Google Colab notebook to see traces in under 5 minutes.
Why Tracing matters
- Debug long or failing requests in seconds.
- Audit prompts & completions for compliance and safety.
- Attribute quality and cost back to specific services or users.
- Feed production traffic into evaluations.
If you call it something else
- Observability / AI spans / request logs: We capture standard OpenTelemetry traces and spans for LLM calls and related operations.
- Agent runs / tools / function calls: These appear as nested spans in the trace tree, with inputs/outputs when available.
- Prompt/Completion pairs: Extracted from common keys (
openinference.*,ai.prompt/ai.response,gen_ai.*) so they can be turned into testcases and scored.
Instrumentation Methods
Choose the method that fits your stack. All methods send traces to Scorecard’s OpenTelemetry endpoint.- Agent Frameworks
- SDK Wrappers
- Traceloop
- LLM Proxy
- OpenTelemetry
For frameworks with built-in OpenTelemetry support (Claude Agent SDK, OpenAI Agents SDK). No code changes—just set environment variables.See the Claude Agent SDK Tracing guide for details.
View Traces in the Records Page
Ingested traces appear on the Records page alongside records from other sources (API, Playground, Kickoff). Each row in the table shows: Each row shows the record’s inputs, outputs, status, source, trace ID, and metric scores. You can search by inputs, outputs, and expected values, or filter bystatus, source, trace.id, run.id, testcase.id, metric, metadata, time range, and more. Use Quick Filters for presets like “My Recent Records”. Customise visible columns via the Edit Table modal.
Open a record to see its trace detail panel, which breaks the trace into four tabs: Conversation, Timeline, Chat, and Debug. For chat-based traces, the Conversation tab replays the trace as user messages, assistant responses, and tool calls:
The Debug tab pairs the full span tree with a trace overview (duration, cost, tokens, and model):
Trace Grouping
When running batch operations or multi-step workflows, you can group related traces into a single run using thescorecard.tracing_group_id span attribute. This makes it easier to track and analyze workflows that span multiple LLM calls.
How it works
Add thescorecard.tracing_group_id attribute to your spans with a shared identifier. Scorecard automatically groups spans with the same group ID into a single run.
Use cases
- Batch processing: Group all documents processed in a single batch job
- Multi-step agents: Track all LLM calls within an agent’s execution
- Workflows: Link related operations across different services
- A/B testing: Group traces by experiment variant for comparison
AI-Specific Error Detection
Scorecard’s tracing detects AI-specific behavioral issues that standard observability misses, not just technical failures. It analyzes every interaction for both technical errors and behavioral problems.Silent Failure Detection
A “silent failure” is when your AI responds, but incorrectly. These often go unnoticed without AI-specific observability. Scorecard automatically detects behavioral errors including off-topic responses, workflow interruptions, safety violations, hallucinations, and context loss. Technical errors like rate limits, timeouts, and API failures are captured automatically through standard trace error recording. AI applications also face issues that error logs don’t capture: semantic drift, safety policy violations, factual accuracy problems, and task completion failures.Custom Error Detection
Create custom metrics in Scorecard’s UI to catch application-specific issues. An AI-powered metric can analyze trace data for things like off-topic responses, safety violations, or task completion failures, then automatically flag the traces that match.Supported Frameworks & Providers
Scorecard traces LLM applications built with popular open-source frameworks through OpenLLMetry. OpenLLMetry provides automatic instrumentation for:Application Frameworks
- CrewAI – Multi-agent collaboration
- Haystack – Search and question-answering pipelines
- LangChain – Chains, agents, and tool calls
- Langflow – Visual workflow builder
- LangGraph – Multi-step workflows and state machines
- LiteLLM – Unified interface for 100+ LLMs
- LlamaIndex – RAG pipelines and document retrieval
- OpenAI Agents SDK – Assistants API and function calling
- Vercel AI SDK – Full-stack AI applications
LLM Providers
- Aleph Alpha
- Anthropic
- AWS Bedrock
- AWS SageMaker
- Azure OpenAI
- Cohere
- Google Gemini
- Google Vertex AI
- Groq
- HuggingFace
- IBM Watsonx AI
- Mistral AI
- Ollama
- OpenAI
- Replicate
- Together AI
- and more
Vector Databases
- Chroma
- LanceDB
- Marqo
- Milvus
- Pinecone
- Qdrant
- Weaviate
For the complete list of supported integrations, see the OpenLLMetry repository. All integrations are built on OpenTelemetry standards and maintained by the community.
Custom Providers
For frameworks or providers not listed above, you can use:- HTTP Instrumentation: OpenLLMetry’s
instrument_http()for HTTP-based APIs - Manual Spans: Emit custom OpenTelemetry spans for proprietary systems
Use cases
- Production observability for LLM quality and safety
- Debugging slow/failed requests with full span context
- Auditing prompts/completions for compliance
- Attributing token cost and latency to services/cohorts
- Building evaluation datasets from real traffic (Trace to Testcase)
Next steps
- Follow the Tracing Quickstart to send your first trace.
- Set up Claude Agent SDK Tracing with zero code changes.
- Instrument LangChain chains and agents.
- Use the Vercel AI SDK wrapper for full-stack AI apps.
- Open the Colab notebook for an interactive tour.