Alerts put the grid on watch
Create persistent monitors from the map, Radar, or an asset page—and receive evidence-backed email when the condition activates or recovers.
The grid does not wait for someone to have the right dashboard open. Alerts turns a live observation into a persistent rule that keeps evaluating after you leave Ask the Grid.
Create the rule in context
Alerts begins in the interfaces operators already use. Select a node on the map, open a Radar metric, visit an individual asset, select several nodes, draw an area, or drop a pin. The composer opens as a global right-side panel and keeps the map or dashboard visible while you define the rule.
The selected grid, asset, area, or metric is carried into the draft. That removes the most failure-prone step in traditional alert builders: reconstructing the thing you were looking at in a separate configuration screen.

Watch values, not dashboards
Value alerts cover operational questions such as nodal price crossing a fixed level, ERCOT system load exceeding a threshold, or a forecast moving outside an expected range. Choose an operator, threshold, lookback, confirmation window, and recovery rule so a transient spike does not become a noisy incident.
A rule can alert once, require repeated evidence before activating, and wait for a recovery band before resolving. Missing or delayed source data is handled separately from the monitored condition, so silence is not mistaken for normal.

Watch the operational event stream
Not every important change is a number. Event alerts can watch for new outages, operator notices, reliability actions, and other grid events. Scope them to the whole ISO, an asset, or a geographic area and filter by event category or severity.
The alert records what changed, when the source observed it, and the evidence used to change state. That makes the notification a starting point for investigation rather than an unexplained bell.

Turn geography into a monitor
Map-native scopes make alerting geotemporal. A dropped pin can watch a radius for new activity. Multi-select can watch a chosen set of nodes. Area and grid scopes support broader questions such as whether a new event or asset appears inside the operating footprint.
The first beta focuses on clear, inspectable scopes. Custom polygons and richer spatial relationships are part of the direction, but the rule always shows exactly which geometry and entities it evaluates.

Operate the monitor, not just the notification
The Alerts manager shows active and paused rules, their source health, current value, evaluation cadence, and recent evidence history. Rules can be edited, cloned in a paused state, tested by email, paused, resumed, or archived.
Alerts ships as an opt-in beta. Sign in, enable it from the Alerts preview or Settings → Experiments, and the manager plus contextual actions appear across the product. Turning the experiment off pauses every active rule.
Email delivery is included with a free account. Enterprise workspaces can add team routing to Slack and custom notification endpoints. Slack configuration is presented as an Enterprise path in this beta; delivery integration follows as a separate rollout.
Alerts is a beta cornerstone for Ask the Grid: one monitoring model across Radar values, map geography, grid events, and individual assets. The goal is simple—put the grid on watch, and come back when the evidence says the state changed.
