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.

Practice

1. What is the main purpose of a resource monitor in Snowflake?

easy

A. To track and control cloud credit usage by setting limits

B. To create new virtual warehouses automatically

C. To backup data to external storage

D. To manage user access permissions

Solution

1. Step 1: Understand resource monitor function

   Resource monitors are designed to track cloud credit consumption and enforce limits to control costs.

2. Step 2: Identify the correct purpose

   Among the options, only tracking and controlling credit usage matches the resource monitor's role.

3. Final Answer:

   To track and control cloud credit usage by setting limits -> Option A

4. Quick Check:

   Resource monitor = cost control [OK]

Hint: Resource monitors limit cloud credits to control costs [OK]

Common Mistakes:

• Confusing resource monitors with user access controls
• Thinking resource monitors create warehouses
• Assuming resource monitors handle data backups

2. Which Snowflake SQL command correctly creates a resource monitor with a 1000 credit monthly limit?

easy

A. CREATE RESOURCE MONITOR my_monitor WITH CREDIT_QUOTA = 1000, TRIGGERS ON 90 PERCENT DO NOTIFY

B. CREATE RESOURCE MONITOR my_monitor SET CREDIT_LIMIT = 1000

C. CREATE RESOURCE MONITOR my_monitor WITH CREDIT_QUOTA = 1000 TRIGGERS ON 90 PERCENT DO NOTIFY

D. CREATE RESOURCE MONITOR my_monitor CREDIT_LIMIT 1000

Solution

1. Step 1: Review correct syntax for resource monitor creation

   The correct syntax uses CREATE RESOURCE MONITOR with WITH CREDIT_QUOTA and TRIGGERS clauses.

2. Step 2: Match syntax with options

   CREATE RESOURCE MONITOR my_monitor WITH CREDIT_QUOTA = 1000 TRIGGERS ON 90 PERCENT DO NOTIFY matches the correct syntax including triggers and notification on 90% usage.

3. Final Answer:

   CREATE RESOURCE MONITOR my_monitor WITH CREDIT_QUOTA = 1000 TRIGGERS ON 90 PERCENT DO NOTIFY -> Option C

4. Quick Check:

   Correct syntax uses WITH CREDIT_QUOTA and TRIGGERS [OK]

Hint: Use WITH CREDIT_QUOTA and TRIGGERS to create monitors [OK]

Common Mistakes:

• Using SET instead of WITH for quota
• Omitting TRIGGERS clause
• Incorrect keyword CREDIT_LIMIT instead of CREDIT_QUOTA

3. Given this resource monitor configuration:

CREATE RESOURCE MONITOR rm1 WITH CREDIT_QUOTA = 500 TRIGGERS ON 80 PERCENT DO NOTIFY ON 100 PERCENT DO SUSPEND;

What happens when the credit usage reaches 100%?

medium

A. The resource monitor suspends the warehouses linked to it

B. Snowflake sends a notification but continues running

C. The credit quota automatically increases

D. Nothing happens automatically

Solution

1. Step 1: Analyze the triggers in the resource monitor

   The monitor triggers a notification at 80% and suspends resources at 100% usage.

2. Step 2: Understand the effect of the 100% trigger

   At 100%, the monitor suspends warehouses linked to it to prevent further credit use.

3. Final Answer:

   The resource monitor suspends the warehouses linked to it -> Option A

4. Quick Check:

   100% trigger with SUSPEND = suspend warehouses [OK]

Hint: 100% trigger with SUSPEND stops warehouses automatically [OK]

Common Mistakes:

• Thinking notification happens at 100% instead of suspend
• Assuming quota increases automatically
• Believing nothing happens at limit

4. You wrote this command to create a resource monitor:

CREATE RESOURCE MONITOR monitor1 WITH CREDIT_QUOTA = 2000 TRIGGERS ON 90 PERCENT DO NOTIFY ON 110 PERCENT DO SUSPEND;

What is wrong with this command?

medium

A. CREDIT_QUOTA must be less than 1000

B. The trigger percentage cannot exceed 100%

C. DO NOTIFY is not a valid action

D. Resource monitors cannot suspend warehouses

Solution

1. Step 1: Check trigger percentage limits

   Trigger percentages must be between 0 and 100; 110% is invalid.

2. Step 2: Validate other parts of the command

   DO NOTIFY is valid, CREDIT_QUOTA can be any positive number, and suspension is allowed.

3. Final Answer:

   The trigger percentage cannot exceed 100% -> Option B

4. Quick Check:

   Trigger percent ≤ 100% [OK]

Hint: Trigger percentages must be 0-100% only [OK]

Common Mistakes:

• Setting trigger above 100%
• Confusing DO NOTIFY syntax
• Thinking suspension is disallowed

5. You want to prevent unexpected high costs by automatically suspending warehouses when 95% of your monthly credit quota is used, and notify at 80%. Which resource monitor configuration achieves this?

hard

A. CREATE RESOURCE MONITOR cost_control WITH CREDIT_QUOTA = 1500 TRIGGERS ON 95 PERCENT DO NOTIFY ON 80 PERCENT DO SUSPEND;

B. CREATE RESOURCE MONITOR cost_control WITH CREDIT_QUOTA = 1500 TRIGGERS ON 100 PERCENT DO NOTIFY ON 95 PERCENT DO SUSPEND;

C. CREATE RESOURCE MONITOR cost_control WITH CREDIT_QUOTA = 1500 TRIGGERS ON 80 PERCENT DO SUSPEND ON 95 PERCENT DO NOTIFY;

D. CREATE RESOURCE MONITOR cost_control WITH CREDIT_QUOTA = 1500 TRIGGERS ON 80 PERCENT DO NOTIFY ON 95 PERCENT DO SUSPEND;

Solution

1. Step 1: Identify notification and suspension percentages

   Notification should occur at 80%, suspension at 95% usage.

2. Step 2: Match triggers to correct actions and order

   CREATE RESOURCE MONITOR cost_control WITH CREDIT_QUOTA = 1500 TRIGGERS ON 80 PERCENT DO NOTIFY ON 95 PERCENT DO SUSPEND; correctly sets 80% for notification and 95% for suspension.

3. Step 3: Verify other options

   The other options swap actions or percentages incorrectly or notify at 100% instead of 80%.

4. Final Answer:

   CREATE RESOURCE MONITOR cost_control WITH CREDIT_QUOTA = 1500 TRIGGERS ON 80 PERCENT DO NOTIFY ON 95 PERCENT DO SUSPEND; -> Option D

5. Quick Check:

   Notify 80%, suspend 95% = CREATE RESOURCE MONITOR cost_control WITH CREDIT_QUOTA = 1500 TRIGGERS ON 80 PERCENT DO NOTIFY ON 95 PERCENT DO SUSPEND; [OK]

Hint: Notify lower %, suspend higher % to control costs [OK]

Common Mistakes:

• Swapping notify and suspend percentages
• Setting notify higher than suspend
• Using 100% notify instead of 80%