Create a Snowflake resource monitor to cap warehouse credit spend and auto-suspend at a threshold
domain: docs.snowflake.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create the monitor with CREATE RESOURCE MONITOR <name> WITH CREDIT_QUOTA = <n> FREQUENCY = MONTHLY START_TIMESTAMP = IMMEDIATELY.
Add one or more TRIGGERS clauses (e.g. ON 75 PERCENT DO NOTIFY, ON 100 PERCENT DO SUSPEND, ON 110 PERCENT DO SUSPEND_IMMEDIATE) to define graduated responses as usage approaches quota.
Assign the monitor to one or more warehouses via ALTER WAREHOUSE <name> SET RESOURCE_MONITOR = <monitor_name>, or set it as the account-level monitor for global enforcement.
Configure NOTIFY_USERS with the Snowflake usernames who should receive threshold notifications.
Test by temporarily lowering CREDIT_QUOTA and running workload to confirm SUSPEND/SUSPEND_IMMEDIATE actions fire as configured, then reset the quota.
Known gotchas
SUSPEND lets currently running queries finish before suspending the warehouse, so spend can still briefly exceed quota; SUSPEND_IMMEDIATE cancels running queries.
An account-level resource monitor combines with warehouse-level monitors; misconfiguring both can suspend warehouses earlier than expected.
CREDIT_QUOTA resets on the configured FREQUENCY interval; a monitor with FREQUENCY = NEVER does not reset and stays suspended until manually reset.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?