Resource monitors for cost control in Snowflake - Step-by-Step Execution

Process Flow - Resource monitors for cost control

Create Resource Monitor

↓

Set Credit Quota Limit

↓

Assign to Warehouses

↓

Monitor Usage

↓

Check if Usage > Quota?

No→Continue Monitoring

Yes↓

Trigger Alert or Suspend Warehouse

↓

Reset or Adjust Monitor

This flow shows how a resource monitor is created, assigned, and tracks usage to control costs by alerting or suspending warehouses when limits are exceeded.

Execution Sample

Snowflake

CREATE RESOURCE MONITOR my_monitor
  WITH CREDIT_QUOTA = 100
  TRIGGERS ON 90 PERCENT DO NOTIFY
  ON 100 PERCENT DO SUSPEND;
ALTER WAREHOUSE my_warehouse SET RESOURCE_MONITOR = my_monitor;

This code creates a resource monitor with a 100 credit limit and triggers notifications at 90% usage and suspends the warehouse at 100%, then assigns it to a warehouse.

Process Table

Step	Action	Credit Usage	Condition Checked	Resulting Action
1	Create resource monitor with 100 credit quota	0	N/A	Monitor created
2	Assign monitor to warehouse	0	N/A	Warehouse linked to monitor
3	Warehouse runs queries, usage = 50 credits	50	50 < 90%	Continue monitoring
4	Warehouse usage reaches 90 credits	90	90% reached	Send notification alert
5	Warehouse usage reaches 100 credits	100	100% reached	Suspend warehouse
6	Warehouse suspended, usage reset or adjusted	0	Monitor reset or adjusted	Monitoring continues
7	Usage remains below quota	30	30 < 90%	Continue monitoring

💡 Warehouse usage stays below quota or is suspended when 100% quota is reached

Status Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	After Step 6	After Step 7
Credit Usage	0	50	90	100	0	30
Monitor State	Created	Active	Alert Sent	Warehouse Suspended	Reset	Active

Key Moments - 3 Insights

Why does the warehouse get suspended at 100 credits usage?

Because the resource monitor is set to suspend the warehouse when usage reaches 100% of the quota, as shown in step 5 of the execution_table.

What happens when usage reaches 90 credits but not 100?

A notification alert is sent to warn about high usage, but the warehouse continues running, as shown in step 4.

Can the monitor usage reset after suspension?

Yes, after suspension, the monitor can be reset or adjusted to continue monitoring, as shown in step 6.

Visual Quiz - 3 Questions

Look at the execution_table, what is the credit usage when the notification alert is sent?

A 90 credits

B 100 credits

C 50 credits

D 30 credits

💡 Hint

Check step 4 in the execution_table where the alert is triggered.

At which step does the warehouse get suspended due to credit usage?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Look for the step where the action is 'Suspend warehouse' in the execution_table.

If the credit quota was increased to 200, how would the suspension step change?

A Suspension would happen at 180 credits

B Suspension would happen at 200 credits

C Suspension would happen at 100 credits

D Suspension would never happen

💡 Hint

Suspension happens at 100% of the quota, so check the quota value in the variable_tracker.

Concept Snapshot

Resource monitors track credit usage to control Snowflake costs.
Set a credit quota limit and assign the monitor to warehouses.
Triggers can notify or suspend warehouses at usage thresholds.
Monitor usage continuously and act when limits are reached.
Reset or adjust monitors after suspension to continue control.

Full Transcript

Resource monitors in Snowflake help control costs by tracking how many credits warehouses use. First, you create a resource monitor with a credit quota limit, like 100 credits. Then, you assign this monitor to one or more warehouses. As the warehouse runs queries, the monitor tracks credit usage. When usage reaches 90% of the quota, it sends a notification alert. If usage hits 100%, the monitor suspends the warehouse to stop further costs. After suspension, the monitor can be reset or adjusted to continue monitoring. This process helps keep cloud costs predictable and controlled.