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

# Alert enrichment

> Automatically gather context the moment an alert fires

When a production alert fires, the first thing your team does is scramble for context - pulling up dashboards, searching logs, checking recent deploys. Wild Moose does all of this automatically, posting the results as a threaded reply within seconds.

## Automatic enrichment

Wild Moose continuously monitors your channels and automatically triggers investigations when it detects something worth looking into - alerts, incidents, and other signals. Here's what happens:

1. **Matches** the event to the right investigation workflow.
2. **Extracts** key attributes (service name, environment, host, etc.) from the context.
3. **Runs** actions against your connected observability tools.
4. **Posts** a structured enrichment thread with findings, root cause analysis, and links to relevant dashboards.

<Info>
  Automatic enrichment runs without any human intervention. Your on-call engineer sees the event and the investigation results at the same time.
</Info>

## On-demand enrichment

You can also trigger investigations manually using commands in Slack or Teams, or programmatically via the [Execution API](/api-reference/introduction).

## What's in an enrichment?

A typical enrichment thread includes:

| Section                   | Description                                                |
| ------------------------- | ---------------------------------------------------------- |
| **Root cause analysis**   | AI-generated summary of what went wrong and why            |
| **Action results**        | Key findings from each action (metrics, logs, traces)      |
| **Dashboard links**       | Direct links to relevant views in your observability tools |
| **Suggested mitigations** | Actionable steps to resolve the issue                      |

<Tip>
  Enrichment results link directly to the source tool (e.g., a Datadog dashboard or Grafana panel) so your team can dive deeper when needed.
</Tip>