Skip to main content

Overview

The Trace Explorer is the central view for monitoring your LLM applications. Every interaction captured by the Python SDK or Proxy integration appears here as a structured trace with full request-response data, performance metrics, and detection results. Open the Trace Explorer at app.avaliar.ai/traces.

Trace Types

Avaliar captures traces from two integration paths. Each path stores slightly different metadata depending on the source.
Traces created by the @traceable decorator in the Python SDK. These include:
FieldDescription
Trace IDUnique identifier for the trace
Span typellm, tool, agent, or generic
ModelThe model used (e.g., gpt-4o, claude-sonnet-4-20250514)
ProviderThe LLM provider (e.g., openai, anthropic)
InputThe prompt or messages sent to the model
OutputThe model’s response
LatencyEnd-to-end execution time
TokensPrompt tokens, completion tokens, and total
CostEstimated cost based on model pricing
Detection modelocal, cloud, or none
Environmentdevelopment, staging, or production
IssuesAny safety issues detected
The Trace Explorer provides several ways to find specific traces:
  • Search — Search by trace ID or model name using the search bar
  • Environment filter — Filter by development, staging, or production
  • Severity filter — Show only traces with issues of a specific severity level
  • Issue type filter — Filter by issue type (e.g., prompt_injection, toxicity, pii)
  • Sort — Sort results by timestamp, model, latency, or cost
Combine multiple filters to narrow down to exactly the traces you need.

Live Mode

Enable Live Mode to auto-refresh the Trace Explorer every 30 seconds. New traces appear at the top of the list without a manual page reload.
Live Mode is useful when you are actively testing or deploying changes and want to watch traces arrive in real time.

Trace Detail View

Click any trace to open the detail view. The detail panel shows:
1

Prompt and Response

The full prompt (or message array) and the model’s response. Responses are rendered as Markdown for readability.
2

Detected Issues

A list of all issues found by the detection pipeline. Each issue shows its type, severity badge, confidence score, and the excerpt that triggered the finding.
3

Performance Metrics

Key metrics for the trace:
MetricDescription
LatencyEnd-to-end execution time in milliseconds
Prompt tokensNumber of tokens in the input
Completion tokensNumber of tokens in the output
Total tokensCombined token count
CostEstimated cost in USD
4

Trace Tree

For SDK traces with nested spans, the trace tree shows the full execution flow as a parent-child hierarchy. Each node displays its span type, latency, and status.
Use the trace tree view to see the full execution flow of nested @traceable calls. This is especially useful for debugging multi-step pipelines like RAG workflows or agent loops.

Trace States

Every trace moves through one of three states after ingestion:
StateBadgeDescription
PendingPendingThe detection pipeline is still processing this trace.
Issues FoundIssuesOne or more safety issues were detected. The severity badge reflects the highest severity found.
CleanCleanDetection completed and no issues were found.
Traces in the Pending state typically resolve within a few seconds. If a trace stays pending for longer than 30 seconds, check the Architecture overview for details on async processing.

Next Steps

Analytics

View aggregated metrics and trends across all your traces.

Alerts

Configure notifications for safety issues detected in your traces.