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

# Alert sources

> Have Ordyn investigate the alerts and issues you already get, from Slack, Linear, Jira, and Asana.

Ordyn triages its own monitors automatically. To have it triage alerts and issues that arrive elsewhere, turn on **Auto-investigate** per source on the **Triage** page.

| Source | What Ordyn watches | Where results go |
| - | - | - |
| **Slack** | New top-level messages in channels you enable | A reply in the message's thread |
| **Linear** | New issues in teams you enable | A comment on the issue |
| **Jira** | New issues in projects you enable | A comment on the issue |
| **Asana** | New tasks in projects you enable | A comment on the task |

Ordyn ignores its own messages and replies inside threads, so one alert produces one investigation.

## Keyword filters

Each source can have **include** and **exclude** keywords, one per line. Matching is case-insensitive, matches substrings, and supports `*` as a wildcard.

| Include set | Exclude set | Behavior |
| - | - | - |
| Yes | Yes | Must match an include keyword and not match any exclude keyword |
| Yes | No | Must match an include keyword |
| No | Yes | Investigated unless an exclude keyword matches |
| No | No | Slack: Ordyn decides whether the message is an actionable alert. Linear, Jira, Asana: every new item is investigated |

Keyword matching is deterministic and instant. When keywords are set, they decide, not the AI.

**Production only**

**Include:** `production`, `critical`, `P0`

**Exclude:** `staging`, `test`, `resolved`

**Errors**

**Include:** `error`, `exception`, `OOMKilled`, `crash*`, `timeout`

**Exclude:** `recovered`, `flaky-test`

**Specific services**

**Include:** `payments*`, `checkout*`

**Exclude:** `canary`

## Tips

* Start with a few high-signal include keywords and widen from there.
* Use exclude keywords for staging, test alerts, and recovery notices.
* Check the **Episodes** page after a week and adjust. Held alerts tell you what Ordyn decided not to surface.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.