What you will be able to do
- Explain what a resource monitor tracks, and why serverless features need a budget instead
- Configure a credit quota and schedule, and predict when used credits reset
- Choose between Notify, Suspend and Suspend Immediate actions and know what resuming takes
- Work out what happens when an account monitor and a warehouse monitor overlap
Key concept
Snowflake credit — The unit Snowflake uses to measure compute consumption. Credits are used only while something is doing work, such as a running warehouse or the cloud services layer. Resource monitors count credits, warehouse sizes are priced in credits, and the usage views report credits.
1.What a resource monitor watches, and what it ignores
A virtual warehouse uses credits for as long as it runs. How many it uses depends on its size and how long it runs. A resource monitor is a first-class Snowflake object that tracks this consumption. It can send alerts when usage crosses thresholds you set, and it can stop warehouses from using more credits. It also counts the cloud services credits needed to support those warehouses.
The limit on its scope matters. Resource monitors only see warehouses. Snowflake also runs serverless features, such as Snowpipe, automatic reclustering and materialized views, and AI services on compute that Snowflake manages. A resource monitor never sees that spend. To track or cap it, Snowflake points you to a different object: a budget. So if an exam scenario needs a spending limit that covers several warehouses plus serverless features, a resource monitor alone can't meet it.
The second rule is who can create monitors. Only ACCOUNTADMIN can create one. An account administrator can grant other roles privileges to view and modify existing monitors, so day-to-day monitoring can be handed off without handing out ACCOUNTADMIN.
Checkpoint 1 of 5· Check yourself
A FinOps team wants automatic alerts when credit consumption by Snowpipe and automatic reclustering passes a limit. What should they use?
Resource monitors only cover warehouses, including at account level. Spend on serverless features and AI services is tracked with a budget.
“To monitor credit consumption by these features, use a budget instead.”Source: docs.snowflake.com
2.Credit quota and schedule
The credit quota is the number of credits the monitor allows per frequency interval, and it can be any number. Snowflake tracks credits used by every warehouse assigned to the monitor and resets the count to 0 at each interval. The quota counts warehouse compute and the cloud services those warehouses use. Snowflake's example: with a 1,000-credit limit, 700 warehouse credits plus 300 cloud services credits in one interval triggers the alert. This is the raw count. Even cloud services credits that are later forgiven under the daily 10% adjustment count toward the limit.
By default, a monitor starts tracking immediately and resets at the start of each calendar month, which is the start of the standard billing cycle. You can customise the schedule:
- Frequency: Daily, Weekly, Monthly, Yearly or Never. With Never, used credits never reset, so warehouses keep running until they reach the quota. - Start: immediately or at a future timestamp. Resets are counted from this date, but always happen at 12:00 AM UTC, whatever time you give. A start on the last day of a month resets on the last day of every later month. - End: a timestamp when the monitor suspends its warehouses, whether or not any threshold was reached. Snowflake notes this property isn't commonly used.
Frequency and start go together: if you set one, you must set the other. A monitor that has a quota but isn't assigned to the account or to any warehouse doesn't track anything. It stays dormant.
Checkpoint 2 of 5· Check yourself
A monitor has Frequency = Weekly and starts Monday 15 July at 8:00 AM. When do its used credits reset?
The start date sets which day the reset falls on. The time is always midnight UTC, whatever time you put in the start timestamp.
“regardless of the time specified in the start date and time, resource monitors reset at 12:00 AM UTC”Source: docs.snowflake.com
3.Actions: notify, suspend, suspend immediately
A monitor acts through actions, also called triggers. Each action pairs a threshold, given as a percentage of the credit quota, with what to do when usage reaches it. Thresholds can be above 100, so you can let a warehouse go a little over quota before acting.
| Action | Effect on standard warehouses | Running statements | Allowed per monitor |
|---|---|---|---|
| Notify | No action on warehouses; sends a notification | Unaffected | Up to five |
| Notify & Suspend | Suspends all assigned warehouses | Allowed to complete first | One |
| Notify & Suspend Immediately | Suspends all assigned warehouses at once | Cancelled | One |
For Adaptive Warehouses, the suspend actions disable the warehouse instead: after running statements finish, or immediately. A common pattern is a few Notify actions at rising percentages, then Suspend, then Suspend Immediate as a hard stop. A monitor needs at least one action. With none, nothing happens when usage reaches a threshold.
Suspension doesn't end on its own. Once a suspend action fires, the warehouses can't run new queries until the monitor's credit quota is increased. Under the default schedule, the monthly reset also clears the count. With Frequency = Never, there's no reset, so raising the quota (or reassigning the warehouses) is the way back.
Notifications go to every account administrator who has notifications turned on. Non-administrator users can also be enabled to receive email notifications, but only for warehouse monitors, not for the account monitor.
Checkpoint 3 of 5· Check yourself
An account monitor with Frequency = Never and a 10,000-credit quota has just fired its Suspend action. What lets the warehouses run queries again?
With Never, used credits never reset, so the warehouses stay suspended until the quota is raised.
“No new queries can be executed by the warehouses until the credit quota for the resource monitor is increased.”Source: docs.snowflake.com
Checkpoint 4 of 5· Exam question
A finance team wants every warehouse in the account to stop consuming credits the moment monthly spend hits a hard cap, even if that means killing queries that are mid-execution. Which resource monitor action produces this behavior?
Correct answer: A — Configure a Suspend Immediately action at the target credit threshold
- A. Correct. Suspend Immediately cancels any statements currently executing on the assigned warehouses and suspends them right away, which is the only action that stops credit consumption instantly rather than waiting for running work to finish.
- B. Incorrect. The Suspend action sends a notification and suspends the assigned warehouses only after all currently executing statements complete, so credits keep accruing until those queries finish.
- C. Incorrect. A notification action only alerts administrators when the threshold is reached; it has no effect on warehouse state, so queries and credit consumption continue unaffected.
- D. Incorrect. Auto-suspend only stops a warehouse after it sits idle with no queries; it does not react to a credit threshold and would not interrupt warehouses that are actively running queries.
4.Account monitors, warehouse monitors, and overlap
A monitor's assignment decides what it covers. An account monitor covers every warehouse in the account, and an account can have only one. A warehouse monitor covers only the warehouses assigned to it. An account can have many warehouse monitors, and each can cover one or more warehouses, but each warehouse can belong to only one warehouse monitor.
Snowflake's own example combines both:
| Monitor | Covers | Quota per interval |
|---|---|---|
| Resource Monitor 1 (account) | All five warehouses | 5000 credits |
| Warehouse monitor | Warehouse 3 | 1000 credits |
| Warehouse monitor | Warehouses 4 and 5 combined | 2500 credits |
Neither level takes precedence. Both monitors run at once, and whichever reaches a suspend threshold first suspends the warehouse. Warehouse 3 can stop at its own 1,000 credits. It can also stop earlier if the account as a whole reaches 5,000 first, so warehouses 3, 4 and 5 may never reach their own quotas. Remember too that the account monitor only covers warehouses. It doesn't control serverless compute such as Snowpipe, automatic reclustering or materialized views.
Checkpoint 5 of 5· Check yourself
Warehouse 3 has its own monitor (1,000 credits) and is also covered by the account monitor (5,000 credits). Both have Suspend actions. What happens?
The account monitor doesn't replace warehouse-level assignments. Either monitor can suspend the warehouse when it reaches its threshold.
“An account-level resource monitor does not override resource monitor assignment for individual warehouses.”Source: docs.snowflake.com
Sources1
Exam traps
Each one states something that sounds right. Open it to see what is actually true.
1.An account-level resource monitor caps all credit spend in the account, including Snowpipe and other serverless features.Why is that wrong?
Resource monitors only cover warehouses. Serverless features and AI services need a budget.
Covered in What a resource monitor watches, and what it ignores
2.A resource monitor counts only billed credits, so cloud services usage under the 10% adjustment doesn't count toward the quota.Why is that wrong?
Monitors count all cloud services consumption, including credits that are never billed.
Covered in Credit quota and schedule
3.When a warehouse has its own monitor, the account monitor no longer applies to it, or the other way round.Why is that wrong?
Both monitors apply. Whichever reaches a suspend threshold first suspends the warehouse.
Covered in Account monitors, warehouse monitors, and overlap
Sources
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.
“Resource monitors work for warehouses only.”
↩︎ What a resource monitor watches, and what it ignores“Only users with the ACCOUNTADMIN role can create a resource monitor”
↩︎ What a resource monitor watches, and what it ignores“Credit quota accounts for credits consumed by both user-managed virtual warehouses and virtual warehouses used by cloud services.”
↩︎ Credit quota and schedule“if you specify a frequency, you must also specify a start date and time, and vice versa”
↩︎ Credit quota and schedule“It simply remains dormant.”
↩︎ Credit quota and schedule“Send a notification and suspend all assigned standard warehouses immediately, which cancels any statements being executed by the warehouses at the time.”
↩︎ Actions: notify, suspend, suspend immediately“A resource monitor must have at least one action defined”
↩︎ Actions: notify, suspend, suspend immediately“Non-administrator users can only receive email notifications for warehouse monitors.”
↩︎ Actions: notify, suspend, suspend immediately“An account can only have one account monitor.”
↩︎ Account monitors, warehouse monitors, and overlap“may be less than their quotas if the quota for the account is reached first.”
↩︎ Account monitors, warehouse monitors, and overlap“An account-level resource monitor does not control credit usage by the Snowflake-provided compute resources for serverless features”
↩︎ Exam trap 1“Resource monitor limits do not take into account the daily 10% adjustment for cloud services.”
↩︎ Exam trap 2“An account-level resource monitor does not override resource monitor assignment for individual warehouses.”
↩︎ Exam trap 3“To monitor credit consumption by these features, use a budget instead.”
↩︎ Checkpoint“Resource monitor limits do not take into account the daily 10% adjustment for cloud services.”
↩︎ Prediction“regardless of the time specified in the start date and time, resource monitors reset at 12:00 AM UTC”
↩︎ Checkpoint“An account-level resource monitor does not override resource monitor assignment for individual warehouses.”
↩︎ Checkpoint - 2.
“You can use budgets to control credit usage for compute costs, including those incurred by serverless features.”
↩︎ What a resource monitor watches, and what it ignores - 3.
“Usage for cloud services is charged only if the daily consumption of cloud services exceeds 10% of the daily usage of virtual warehouses.”
↩︎ Credit quota and schedule“A Snowflake credit is a unit of measure, and it is consumed only when a customer is using resources”
↩︎ Key concept - 4.
“Each resource monitor supports up to a maximum of 5 NOTIFY action triggers.”
↩︎ Actions: notify, suspend, suspend immediately“No new queries can be executed by the warehouses until the credit quota for the resource monitor is increased.”
↩︎ Checkpoint