Custom budgets¶

Tag inheritance¶

Adding a tag to a budget tracks all objects with that tag, including objects that have inherited the tag from a parent object. For example, if a database has a tag, then tables within the database inherit the tag and will be tracked by a budget. Because a budget tracks usage based on a tag/value pair, if you override the value of the tag at the table-level, it might change whether the budget tracks usage associated with the table. For example, suppose you have a budget that tracks objects with tag team = 'eng'. If the database has the tag team = 'eng', but a table within the database has tag team = 'IT', the budget won’t monitor costs associated with that table.

In the context of budgets, tags are not inherited from an account because the account budget is intended to fulfill that use case.

For more information, including how tag values are overridden, see Tag inheritance.

Tracking an object with multiple budgets¶

Multiple budgets can add the same tag/value pair, which means more than budget can track credit usage of the same object. For example, suppose you add the tag cost_center = 'eng' to both budget_1 and budget_2. As a warehouse with tag cost_center = 'eng' consumes credits, it will count toward the credit limit of both budget_1 and budget_2.

An object can also be tracked by more than one budget if the object has multiple tags. For example, suppose a warehouse has two tags: cost_center = 'finance' and stage = 'dev'. You could create one budget that tracks cost_center = 'finance' and another that tracks stage = 'dev'. Credits consumed by the warehouse would count toward the credit limit of both budgets.

Limitations and considerations¶

When using tags to monitor objects, keep the following in mind:

• When you change a tag on an object, it can take up to six hours for the change to be reflected in budgets that use tags.

• Currently, compute pools and alerts cannot be monitored with tags. You must add them individually.

• Changes to tags within the first two days of the month are reflected in the prior month’s usage.

Create a custom role to create budgets¶

You can use a custom role to create budgets in your account. For a full list of privileges and roles that must be granted to a role to create a custom budget, see Budgets roles and privileges.

The following example creates a role named budget_owner role and grants the required role and privileges to create custom budgets in the schema budgets_db.budgets_schema. The example must be executed using the ACCOUNTADMIN role:

USE ROLE ACCOUNTADMIN;
   
CREATE ROLE budget_owner;
  
GRANT USAGE ON DATABASE budgets_db TO ROLE budget_owner;
GRANT USAGE ON SCHEMA budgets_db.budgets_schema TO ROLE budget_owner;

GRANT DATABASE ROLE SNOWFLAKE.BUDGET_CREATOR TO ROLE budget_owner;

GRANT CREATE SNOWFLAKE.CORE.BUDGET ON SCHEMA budgets_db.budgets_schema
  TO ROLE budget_owner;

If you want to enable a role other than the budget owner to modify a custom budget’s settings, you can create a custom role with modify privileges. For more information, see Create a custom role to manage a custom budget.

Use Snowsight to create a custom budget¶

1. Sign in to Snowsight.

2. Select Admin » Cost Management.

3. Select Budgets.

4. Select (Add Budget).

5. Enter a Budget name.

6. Select the database and schema in which to create your budget.

7. Enter the Spending limit.

8. Enter the email addresses to receive notifications.

   Note

   Each email address added for budget notifications must be verified. The notification email setup fails if any email address in the list is not verified.

9. Select + Tag & resources, then add the tags and resources that you want to add to the custom budget.

   Note

   • When you select a database or schema, all supported objects (for example, tables) contained within the database or schema are also added to the budget.

   • If you are directly adding individual objects, you can only add an object to one custom budget. In this case, if an object is currently included in one custom budget and you add that object to a second custom budget, Budgets removes the object from the first custom budget without issuing a warning. This behavior does not apply to using tags to add objects to budgets; an object with one or more tags can be included in multiple custom budgets if you are using tags to add the object to the budgets.

After you create and set up a custom budget, you can create a custom role to enable non-account administrators to monitor budget resources and usage. For more information, see Create a custom role to monitor a custom budget.

Use SQL commands to create a custom budget¶

Create a custom budget and then set the spending limit and notification email addresses.

1. Review the existing budgets in your account:

   Note

   The following statement returns the budgets for which you have access privileges. Only a user with the ACCOUNTADMIN role can see all the budgets in the account.

   SELECT SYSTEM$SHOW_BUDGETS_IN_ACCOUNT();
   

   Copy

2. Create budget my_budget in budgets_db.budgets_schema using the CREATE BUDGET command:

   USE SCHEMA budgets_db.budgets_schema;
   
   CREATE SNOWFLAKE.CORE.BUDGET my_budget();
   

   Copy

3. Set the monthly spending limit. For example, set the spending limit to 500 credits per month:

   CALL my_budget!SET_SPENDING_LIMIT(500);
   

   Copy

4. Set up notifications for the budget so that you receive notifications when your credit usage is expected to exceed your spending limits.

   See Notifications for budgets.

After you create and set up a custom budget, you can create a custom role to enable non-account administrators to monitor budget resources and usage. For more information, see Create a custom role to monitor a custom budget.

To add objects to your new budget, see Add or remove objects from a custom budget.

Custom role example¶

Grant the custom role budget_admin the ability to monitor and modify the budget my_budget in schema budgets_db.budgets_schema:

• Grant the required privileges and instance role to custom role budget_admin for budget my_budget in schema budgets_db.budgets_schema:

  GRANT USAGE ON DATABASE budgets_db TO ROLE budget_admin;
  
  GRANT USAGE ON SCHEMA budget_db.budgets_schema TO ROLE budget_admin;
  
  GRANT SNOWFLAKE.CORE.BUDGET ROLE budgets_db.budgets_schema.my_budget!ADMIN
     TO ROLE budget_admin;
  
  GRANT DATABASE ROLE SNOWFLAKE.USAGE_VIEWER TO ROLE budget_admin;
  

  Copy

• Grant the APPLYBUDGET privilege on objects and tags to be added to or removed from a custom budget. This step is required for each object or tag to be added or removed.

  For example, to enable the role budget_admin to add database db1 to custom budget my_budget, execute the following statements:

  GRANT USAGE ON DATABASE db1 TO ROLE budget_admin;
  
  GRANT APPLYBUDGET ON DATABASE db1 TO ROLE budget_admin;
  

  Copy

Use Snowsight to add or remove tags from a custom budget¶

1. Sign in to Snowsight.

2. Select Admin » Cost Management.

3. Select Budgets.

4. Select the budget to edit.

5. In the dashboard, select (edit icon).

6. Select + Tags & resources.

7. Expand Tags and navigate to the tag you want to add.

8. Do one of the following:

   • If the tag has a list of allowed values, select one or more of the values.

   • If the tag can be set to any value, specify the value.

9. Select Done.

Use SQL commands to add or remove tags from a custom budget¶

The role used to add or remove an tag from a budget must have the APPLYBUDGET privilege on the tag. For more information, see the examples in the Create a custom role to manage a custom budget section.

To review the list of tags already in the custom budget, call the budget’s <budget_name>!GET_LINKED_TAGS method. For example, to see the list of tags in the budget my_budget in the budgets_db.budgets_schema schema, execute the following statement:

CALL budgets_db.budgets_schema.my_budget!GET_LINKED_TAGS();

Tags must be added to or removed from a budget by reference.

1. You can add tag cost_mgmt_db.tags.cost_center to budget my_budget by using the following steps:

   1. Grant the APPLYBUDGET privilege on the tag to the role budget_admin by executing the following statement:

      GRANT APPLYBUDGET ON TAG cost_center TO ROLE budget_admin;
      

      Copy

   2. Pass a reference for tag cost_center to the ADD_TAG instance method by executing the following statement. The value of the tag is set to finance.

      CALL budgets_db.budgets_schema.my_budget!ADD_TAG(
         SELECT SYSTEM$REFERENCE('TAG',
            'cost_mgmt_db.tags.cost_center',
            'SESSION',
            'applybudget'),
            'finance');
      

      Copy

      The SYSTEM$REFERENCE function creates a reference for the tag cost_center, with the APPLYBUDGET privilege granted on the tag. This enables the budget to monitor the objects in your account that have the specified tag/value pair in your account. The third parameter to the function specifies the scope for the reference; in this case, ‘SESSION’ creates a reference with session scope. References passed to the ADD_TAG method for a budget can be created with any transient reference scope (that is, the third parameter can be either ‘SESSION’ or ‘CALL’).

2. You can remove the tag cost_center from the budget my_budget by using the following steps:

   1. Grant the APPLYBUDGET privilege on the database to the role budget_admin by executing the following statement:

      GRANT APPLYBUDGET ON TAG cost_center TO ROLE budget_admin;
      

      Copy

   2. Remove the tag by passing a reference to the REMOVE_TAG instance method:

      CALL budgets_db.budgets_schema.my_budget!REMOVE_TAG(
         SELECT SYSTEM$REFERENCE('TAG',
            'cost_mgmt_db.tags.cost_center',
            'SESSION',
            'applybudget'),
            'finance');
      

      Copy

Use Snowsight to add or remove objects from a custom budget¶

1. Sign in to Snowsight.

2. Select Admin » Cost Management.

3. Select Budgets.

4. Select the budget to edit.

5. In the dashboard, select (edit icon).

6. Select + Tags & resources, then select the objects you want to add to the custom budget.

   Note

   • When you select a database or schema, all supported objects (for example, tables) contained within the database or schema are also added to the budget.

   • If you are directly adding individual objects, you can only add an object to one custom budget. In this case, if an object is currently included in one custom budget and you add that object to a second custom budget, Budgets removes the object from the first custom budget without issuing a warning. This behavior does not apply to using tags to add objects to budgets; an object with one or more tags can be included in multiple custom budgets if you are using tags to add the object to the budgets.

7. Select Done.

Use SQL commands to add or remove objects from a custom budget¶

The role used to add or remove an object from a budget must have the APPLYBUDGET privilege on the object. For more information, see the examples in the Create a custom role to manage a custom budget section.

To review the list of objects already in the custom budget, call the budget’s <budget_name>!GET_LINKED_RESOURCES method. For example, to see the list of objects in the budget my_budget in the budgets_db.budgets_schema schema, execute the following statement:

CALL budgets_db.budgets_schema.my_budget!GET_LINKED_RESOURCES();

The statement returns the following output:

+-------------+-----------------+-----------+-------------+---------------+
| RESOURCE_ID | NAME            | DOMAIN    | SCHEMA_NAME | DATABASE_NAME |
|-------------+-----------------+-----------+-------------+---------------|
|         326 | DB1             | DATABASE  | NULL        | NULL          |
|         157 | MY_WH           | WAREHOUSE | NULL        | NULL          |
+-------------+-----------------+-----------+-------------+---------------+

Objects must be added to or removed from a budget by reference.

1. You can add table t1 to budget my_budget by using the following steps:

   1. Grant the APPLYBUDGET privilege on the table to the role budget_admin by executing the following statement:

      GRANT APPLYBUDGET ON TABLE t1 TO ROLE budget_admin;
      

      Copy

   2. Pass a reference for table t1 to the ADD_RESOURCE instance method by executing the following statement:

      CALL budgets_db.budgets_schema.my_budget!ADD_RESOURCE(
         SELECT SYSTEM$REFERENCE('TABLE', 't1', 'SESSION', 'applybudget'));
      

      Copy

      The SYSTEM$REFERENCE function creates a reference for a TABLE object, t1, with the APPLYBUDGET privilege granted on the table. This enables the budget to monitor the specified object in your account. The third parameter to the function specifies the scope for the reference; in this case, ‘SESSION’ creates a reference with session scope. References passed to the ADD_RESOURCE method for a budget can be created with any transient reference scope (that is, the third parameter can be either ‘SESSION’ or ‘CALL’).

      Note

      If you want to add a Snowflake Native App to a budget, when you call SYSTEM$REFERENCE, specify 'DATABASE' (not 'APPLICATION') for the object_type argument.

      For a full list of objects and privileges, see Supported object types and privileges for references.

      Note

      If you are directly adding individual objects, you can only add an object to one custom budget. In this case, if an object is currently included in one custom budget and you add that object to a second custom budget, Budgets removes the object from the first custom budget without issuing a warning. This behavior does not apply to using tags to add objects to budgets; an object with one or more tags can be included in multiple custom budgets if you are using tags to add the object to the budgets.

2. You can remove the database db1 from the budget my_budget by using the following steps:

   1. Grant the APPLYBUDGET privilege on the database to the role budget_admin by executing the following statement:

      GRANT APPLYBUDGET ON DATABASE db1 TO ROLE budget_admin;
      

      Copy

   2. Remove the database by passing a reference to the REMOVE_RESOURCE instance method:

      CALL budgets_db.budgets_schema.my_budget!REMOVE_RESOURCE(
         SELECT SYSTEM$REFERENCE('DATABASE', 'db1', 'SESSION', 'applybudget'));
      

      Copy