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

# Monitors

> Configure the event sources your agents listen to: webhooks, polling integrations, and active checks.

<Note>
  Monitors are the event sources for your agents. Each monitor connects to an external tool, polls an API, or runs an active check.
</Note>

## Monitor types

Clarion supports monitor types across these categories:

* **Identity & Access**: Okta, Microsoft Entra ID, JumpCloud, 1Password, Google Workspace.
* **Cloud**: AWS CloudTrail, AWS GuardDuty, AWS CloudWatch, GCP Cloud Logging, GCP Cloud Monitoring, GCP Security Command Center, Vercel.
* **Source code**: GitHub, Apex.
* **On-chain**: Hypernative, Hexagate, Tenderly.
* **Endpoint**: CrowdStrike Falcon, Huntress.
* **Observability**: Datadog, Grafana, Falco.
* **Infrastructure checks**: DNS zone monitoring, Better Stack uptime alerts.
* **Generic**: Webhook for any tool that can POST JSON.

Each [Integration](/integrations/aws) page describes how to set up monitors for that tool.

## What you can do

* **Create** a monitor or multiple monitors for each connected tool, with type-specific configuration.
* **Filter** which events come through by severity or other criteria the monitor type supports.
* **Enable / disable** monitors without losing configuration.
* **Assign monitors to agents** so the right responder picks up each signal.

<Note>
  Signals from a monitor open an issue only when an alert filter matches them. If you're seeing signals but no issues, check the filters attached to that monitor.
</Note>