Snowflake Warehouse Has No Resource Monitor
Nothing caps this warehouse's spend, so a runaway workload can consume the account's credits before anyone sees a bill.
Free to start. No card. The playground just needs your work email.
Snowflake
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Snowflake, with read-only access to the account.
Explain
Every finding says exactly what to change: Attach a resource monitor to the warehouse.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Snowflake Warehouse on Snowflake
- The fix, by hand
- Open Snowsight → Admin → Cost Management → Resource Monitors → Create.
- Pick a monthly CREDIT_QUOTA matching typical spend with 20% headroom for spikes.
- Add triggers (80% NOTIFY, 100% SUSPEND, 110% SUSPEND_IMMEDIATE) and route NOTIFY to a channel the team monitors.
- Or SQL: CREATE RESOURCE MONITOR the resource_RM WITH CREDIT_QUOTA = ‹n› TRIGGERS ON 80 PERCENT DO NOTIFY ON 100 PERCENT DO SUSPEND ON 110 PERCENT DO SUSPEND_IMMEDIATE;.
- Attach to the warehouse: ALTER WAREHOUSE the resource SET RESOURCE_MONITOR = the resource_RM;.
These are the steps the finding carries in the product.
- Category
- Governance. Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-2118- Full reference
Related checks
See the governance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.