What Resource Monitors Do

A Snowflake resource monitor tracks credit usage for one or more warehouses against a defined quota. When consumption hits a threshold percentage, the monitor triggers an action: notify, suspend at completion, or suspend immediately. Resource monitors can be scoped to the account level or to individual warehouses.

Setting the Right Quota

Set quotas based on historical consumption with a buffer. A warehouse that historically uses 1,000 credits per month should have a quota of 1,200 to 1,500, enough headroom for legitimate growth without allowing runaway consumption. Avoid setting quotas too tight. Over-restrictive monitors that trigger suspensions during legitimate peak periods create operational incidents.

Choosing the Right Action

Three actions are available when a threshold is hit. Notify sends an email alert but does not suspend. Use this for early warning thresholds at 75% of quota. Notify and Suspend alerts and suspends the warehouse after current queries complete. Use this for budget limits on non-critical warehouses. Notify and Suspend Immediately kills running queries. Only use this as a last resort for development and testing warehouses.

Multi-Threshold Configuration

Configure multiple thresholds per monitor to create a graduated response. At 60% notify FinOps team. At 80% notify warehouse owner. At 95% notify warehouse owner and suspend new queries at completion. At 100% suspend and notify leadership. This graduated approach gives teams time to respond before hard limits are enforced.

Avoid Account-Level Suspend Monitors

An account-level resource monitor with a Suspend action will suspend ALL warehouses simultaneously when the quota is reached, including critical ETL, reporting, and application warehouses. Use account-level monitors for notification only. Apply Suspend actions only to warehouse-level monitors where the impact is predictable and scoped.

Reset Frequency and Billing Periods

Resource monitors reset on a defined schedule: daily, weekly, monthly, or custom. Align reset frequency with your billing cycle and team reporting cadence. Monthly resets with quarterly review are the most common configuration for production warehouses.

Go beyond resource monitors with Anavsan

APEX provides workload-level attribution, anomaly detection, and optimization recommendations that resource monitors alone cannot offer, with team accountability built in.

Frequently Asked Questions

A resource monitor tracks credit consumption for one or more warehouses against a defined quota. When usage reaches threshold percentages, it triggers actions like notifications, query suspension, or warehouse shutdown.
Use account-level monitors for notification only. Use warehouse-level monitors for actual enforcement. Never configure account-level monitors to suspend warehouses, as this would shut down all production workloads simultaneously.
Base quotas on 3-month historical consumption plus a 20-30% buffer for legitimate growth. Set graduated thresholds at 60%, 80%, 95%, and 100% with escalating alert actions rather than a single hard limit.