ALERT_ HISTORY views and table function: New columns (Pending)¶
Attention
This behavior change is in the 2026_04 bundle.
For the current status of the bundle, refer to Bundle history.
When this behavior change bundle is enabled, the ACCOUNT_USAGE.ALERT_HISTORY view, the ORGANIZATION_USAGE.ALERT_HISTORY view, and the output of the ALERT_HISTORY table function (in INFORMATION_SCHEMA) include the following new columns:
| Column name | Data type | Description |
|---|---|---|
| RUNBOOK | VARCHAR | URL of a runbook or operational documentation page used to triage this alert when someone is notified (for example, https://docs.example.com/runbooks/alert1). |
| CONFIG | VARIANT | JSON configuration from the alert object. Values are available at runtime to both the condition (IF) and action (THEN) SQL so you can parameterize thresholds, notification targets, or feature flags without changing the alert’s SQL text. |
| WAS_AUTO_SUSPENDED | BOOLEAN | Indicates whether the alert was automatically suspended after crossing a threshold of consecutive failures, which helps you find alerts that were turned off by the system and may need data quality or configuration follow-up. |
Ref: 2239