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

# Alerts

> Watch for tagged entities over a perimeter, get notified, and act.

An **alert** watches for entities carrying chosen **tags**, within a **perimeter**, and
notifies recipients when matching entities are raised.

<Note>
  Alerts are **tag-driven**. To alert on a *metric threshold* (e.g. days of stock ≤ 7),
  you first create a [tagging rule](/en/automation/tags) that tags the matching entities,
  then point an alert at that tag. For the full model see
  [Alerts (reference)](/en/developers/alerts/overview).
</Note>

## What an alert watches

* **Tags** — require tags to be present (**include**) or absent (**exclude**), combined
  with **AND** / **OR**. This is the alert's trigger.
* **Check level** — the granularity evaluated: shop, brand, product, variant, or
  inventory item.

## Perimeter

Restrict the alert to specific **stores, brands, products, taxonomies, or collections**.
Leave a dimension empty to apply it everywhere.

## Trigger types

When an instance is raised it records *why* it fired: **threshold reached**, **threshold
approaching** (with how close), or a **forecasted threshold**.

## Notifications

Set a **frequency** (immediately, hourly, daily, weekly, monthly), the **recipients**, and
the **channel** (email today; SMS and WhatsApp are reserved for the future).

## Instances & evaluation runs

Solya evaluates alerts in an **evaluation run** (manual, scheduled, or via API). A run
checks active alerts, raises instances for new matches, resolves instances that no longer
match, and records structured logs and stats.

Each raised **instance** has a status you manage: **pending → acknowledged → resolved**,
or **archived**. From an instance you can launch a **restock**, **rebalance**, or
**markdown** action directly.

## Working with alerts

<Steps>
  <Step title="Tag what matters first">
    Create [tags and tagging rules](/en/automation/tags) so the entities you care about
    (e.g. low-stock fast movers) are tagged automatically.
  </Step>

  <Step title="Create an alert">
    In **Signals**, add an alert that watches those tags (include/exclude), set the check
    level and perimeter, and configure notifications.
  </Step>

  <Step title="Triage & act">
    Acknowledge, resolve, or archive instances — and convert one into a plan when action is
    needed.
  </Step>
</Steps>