- Automated scoring: Every incoming production trace is automatically processed and scored based on predefined metrics.
- Infrastructure: Processing is powered by Coreweave compute and Coreweave GPUs to ensure scalability across millions of traces.
- Custom metrics: Developers can create specific metrics, such as response length or faithfulness to source material, to help understand exactly how an agent is behaving.
- Gain behavioral insight: Move beyond simple system metrics to understand if your agent is hallucinating, failing to follow conversation patterns, or losing grounding in its evidence.
- Automate alerts: Set up automated triggers that notify your team through tools like Slack when an agent’s performance drops below a certain threshold.
- Accelerate the research loop: Use the scores and failure analyses generated by signals to identify specific weaknesses, which can then be used to kick off the research loop for offline model improvement, data annotation, or reinforcement learning.
Use built-in signals
Signals are preset monitors that automatically evaluate production traces for common quality issues and errors. Each signal uses a benchmarked LLM prompt to classify traces and saves the results as comma-delimited tags representing the detected issues. To start classifying traces immediately, enable signals from the Monitors page. Signals don’t require prompt engineering or scorer configuration. Signals use a W&B Inference model to score traces, so no external API keys are required.Available signals
W&B Weave provides 13 preset signals organized into two groups.Quality signals
Quality signals evaluate successful root-level traces for output quality and safety issues.| Signal | What it detects |
|---|---|
| Hallucination | Fabricated facts or claims that contradict the provided input context |
| Low quality | Responses with poor format, insufficient effort, or incomplete content |
| User frustration | Signs of user frustration such as repeated questions, negative sentiment, or complaints |
| Jailbreaking | Prompt injection and jailbreak attempts that try to bypass safety guidelines |
| NSFW | Explicit, violent, or otherwise inappropriate content in inputs or outputs |
| Lazy | Low-effort responses such as excessive brevity, refusals to help, or deferred work |
| Forgetful | Failure to use context from earlier in the conversation, ignoring previously stated facts or instructions |
Error signals
Error signals categorize failed traces by root cause to help you identify and resolve infrastructure and application issues.| Signal | What it detects |
|---|---|
| Network Error | DNS failures, timeouts, connection resets, and other connectivity issues |
| Ratelimited | HTTP 429 responses, quota exhaustion, and throttling from upstream APIs |
| Request Too Large | Requests exceeding size or token limits, such as context window exceeded |
| Bad Request | Client-side errors where the server rejected the request (4xx except 429) |
| Bad Response | Invalid, unexpected, or unusable responses from remote services (5xx) |
| Bug | Flaws in application code such as KeyError, TypeError, or logic errors |
Enable signals from the Monitors page
To enable signals:- Navigate to wandb.ai and then open your Weave project.
- In the Weave project sidebar, select Monitors.
- At the top of the Monitors page, a row of suggested signal cards appears. Each card shows the signal name, a description, and an + Add signal button.
- To enable a single signal, select the + Add signal button on the signal card. The signal begins scoring new traces immediately.
- To enable multiple signals at once, select the + [X] more signals button. This opens a drawer that lists all available signals grouped by category. Select the signals you want to turn on, then select Add signals.
classifier_meta for the reasoning. For example, the following screenshot shows a high confidence (0.95) that Hallucination didn’t occur and includes a reason for this rating.

Manage active signals
To view or remove active signals:- From the Monitors page, select the Manage signals button (gear icon). This opens a drawer listing all currently active signals grouped by category.
- Hover over a signal and select the Remove signal button (trash icon) to disable the signal.
How signals work
Each signal uses an LLM-as-a-judge approach to classify traces:- Trace selection: Quality signals evaluate successful root-level traces. Error signals evaluate failed traces. Child spans and intermediate calls are not scored.
- Prompt construction: Weave constructs a prompt that includes the trace metadata, inputs, outputs, exception details (if any), and the operation’s source code. The signal’s classifier prompt is appended with instructions for the specific issue to detect.
- LLM scoring: A W&B Inference model evaluates the trace and returns the names of detected issues as comma-delimited string tags (for example,
"Low-quality, User-frustration, Forgetful"). - Result storage: Results are stored as feedback on the Call object and are queryable from the Traces tab.