Alerts & notifications

Vigil sends you the alerts that matter and filters out the noise. The goal is simple: fewer, higher-signal notifications — and a team that acts on the critical ones instead of leaving you to.

Where alerts go

You can route notifications to:

• Slack — a shared channel with your Vigil team
• PagerDuty — for on-call escalation
• Email — for individuals or distribution lists

Tell your Vigil team which destinations you want, and for which severities.

What triggers an alert

Alerts can come from any active module, for example:

• Infrastructure health and availability issues (uptime checks failing, resource saturation)
• New critical or high security findings
• Cost anomalies that break your recent spending baseline
• Pipeline failures and deployment issues (CI/CD)

Reducing noise

Vigil tunes alert thresholds so you aren’t paged for transient or low-value events. Severity-based routing means, for example, critical findings can page on-call while lower-severity items simply appear in the portal and your weekly report.

The human layer

For managed plans, critical alerts aren’t just delivered — your Vigil team investigates and remediates within your response SLA. See Plans & modules for what’s included at each level.

Next: Reports