> ## Documentation Index
> Fetch the complete documentation index at: https://www.adaline.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts

> Get notified when production quality, cost, latency, or error signals need attention

<Note>
  Alerts are currently in beta. Contact [support@adaline.ai](mailto:support@adaline.ai) for private preview access.
</Note>

Alerts help teams react when production behavior crosses a threshold. Use them for signals that need action without waiting for someone to inspect Monitor manually.

## Useful alert signals

Good alert conditions are tied to an operational question:

| Signal               | Example question                                                         |
| -------------------- | ------------------------------------------------------------------------ |
| **Eval score**       | Did quality drop for a prompt, evaluator, release, or environment?       |
| **Error rate**       | Are traces failing above the expected baseline?                          |
| **Latency**          | Did P95 latency exceed the target for a workflow?                        |
| **Cost**             | Did request cost or total spend exceed budget?                           |
| **Token usage**      | Did prompt or completion tokens jump unexpectedly?                       |
| **Metadata segment** | Is a specific environment, route, customer segment, or release affected? |

Use [filters](/docs/monitor/filter-and-search-logs) and [charts](/docs/monitor/analyze-log-charts) to tune the condition before enabling an alert.

## Before creating an alert

Check that:

* The metric is visible and stable in Monitor.
* The relevant traces have meaningful names and metadata.
* The threshold represents user impact, not temporary noise.
* The alert has an owner and response path.
* The team knows where to inspect evidence after it fires.

For quality issues, pair alerts with evaluators and datasets. For latency or cost issues, make sure model, prompt, tool, and environment metadata is available so responders can isolate the cause.

## Respond to an alert

When an alert fires:

1. Open Monitor for the alert window.
2. Open the relevant traces and inspect representative spans.
3. Check whether a Behavior captures the repeated pattern.
4. Add important spans to datasets or update evaluators.
5. Start Improve only when the fix belongs in prompt behavior.

<CardGroup cols={2}>
  <Card title="Analyze log charts" icon="chart-line" href="/docs/monitor/analyze-log-charts">
    Tune alert thresholds from production trends.
  </Card>

  <Card title="Filter, search, export logs" icon="filter" href="/docs/monitor/filter-and-search-logs">
    Find the evidence behind an alert.
  </Card>
</CardGroup>