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

# Alerts

> Monitor intelligence signals and anomalies across your products in real time.

<Note>
  The Alerts feed surfaces signals from your agents, scores, and adapter syncs. Each alert links to the move that caused it. Acknowledge to clear from the feed; act on the move that matters.
</Note>

# Alerts

The Alerts feed surfaces signals generated by your agents and scoring engine. Alerts notify you when something meaningful moves: a dimension drops below a threshold, an adapter sync detects a regression, or an agent surfaces a pattern worth your attention.

Hit **Alerts** in the main nav to see all signals for your account.

## Alert types

<CardGroup cols={2}>
  <Card title="Score regression" icon="arrow-trend-down">
    A dimension or composite dropped meaningfully since the last re-score. Carries before/after values and the affected dimension.
  </Card>

  <Card title="Score improvement" icon="arrow-trend-up">
    A dimension lifted, typically after a team move or re-score. Receipt that something worked.
  </Card>

  <Card title="Threshold breach" icon="triangle-exclamation">
    A metric crossed a configured threshold (delivery velocity dropped below your target, for example). Generated by agent triggers set to event mode.
  </Card>

  <Card title="Adapter signal" icon="plug">
    An adapter sync detected an anomaly: unusual PR patterns, sprint velocity drop, customer signal spike, mapped to a specific dimension.
  </Card>

  <Card title="Agent finding" icon="brain">
    An agent run surfaced a finding that meets your notification criteria. Links to the full agent artifact.
  </Card>

  <Card title="Lifecycle transition" icon="arrows-spin">
    Your lifecycle placement moved based on recent self-assessment progress.
  </Card>
</CardGroup>

## Reading an alert

Each alert carries:

| Field         | Read                                                                |
| ------------- | ------------------------------------------------------------------- |
| **Type**      | Category of the signal (regression, improvement, threshold, others) |
| **Product**   | Which product the alert is about                                    |
| **Dimension** | The specific dimension affected (if applicable)                     |
| **Delta**     | The move in value that triggered the alert                          |
| **Source**    | Whether the alert came from a score, adapter sync, or agent run     |
| **Time**      | When the alert was generated                                        |

## Acknowledging alerts

Alerts stay in your feed until acknowledged. Hit **Acknowledge** on any alert to mark it seen and move it to history. Acknowledging doesn't resolve the underlying move; it just clears the active feed.

<Tip>
  Use acknowledgment as a lightweight triage step. Acknowledge noise, act on signal.
</Tip>

### Filtering

Use the filter bar to show:

* **Unacknowledged only** for alerts waiting on you
* **By product** to focus on a specific product
* **By type** to see only regressions, improvements, or agent findings

## Alert sources

| Source                   | What creates it                                                              |
| ------------------------ | ---------------------------------------------------------------------------- |
| **Scoring engine**       | Every re-score compares against the previous run and generates delta alerts  |
| **Adapter sync**         | Daily sync picks up anomalies in operational signal (GitHub, Linear, others) |
| **Agent triggers**       | Event-based agent triggers fire alerts when conditions are met               |
| **Lifecycle assessment** | Stage transitions surface a notification                                     |

## Alert retention

Alerts are retained for **90 days**, then archived. Acknowledged alerts move to history immediately and stay searchable for the full retention window.

## API access

Retrieve and acknowledge anomalies programmatically:

```bash theme={null}
# List unacknowledged anomalies (paginated)
GET /api/anomalies?severity=high&limit=25

# Acknowledge an anomaly
POST /api/anomalies/acknowledge
{ "anomalyId": "anm_..." }

# Convert an anomaly to a Linear issue
POST /api/anomalies/{id}/convert-to-linear
{ "teamId": "optional-linear-team-id" }

# Adjust detection sensitivity for an event type
POST /api/anomalies/sensitivity
{ "eventType": "pr_cycle_time", "threshold": 3.0 }
```

See [List anomalies](/api-reference/anomalies/list-anomalies), [Acknowledge anomaly](/api-reference/anomalies/acknowledge-anomaly), [Convert to Linear](/api-reference/anomalies/convert-to-linear), and [Set sensitivity override](/api-reference/anomalies/set-sensitivity-override).

Legacy alert listing is available at `GET /api/intelligence/alerts` for backwards compatibility.

<CardGroup cols={2}>
  <Card title="Agent Studio" icon="brain" href="/knowledge-base/agent-studio">
    Configure agents and triggers to generate targeted alerts.
  </Card>

  <Card title="Integrations" icon="plug" href="/knowledge-base/integrations">
    Connect tools to enrich adapter-sourced alerts.
  </Card>
</CardGroup>