Study guide
13.4 Warehouse Monitoring, Alerts, Event Tables & Performance Explorer
SnowPro Advanced: Architect ARA-C01
Track your progress as you read
Finished sections get a check mark.
1 Introduction: The ARA-C01 Exam
About the SnowPro Advanced: Architect (ARA-C01) Exam
2 Chapter 1: Account Strategy & Organization Architecture
1.1 Multi-Account Strategy & Snowflake Organizations 1.2 Snowflake Parameter Hierarchy & Configuration 1.3 Database and Schema Design Architecture
3 Chapter 2: Identity, Access Control & Storage Integrations
2.1 Role-Based Access Control Architecture & Hierarchy 2.2 Secondary Roles, Object Ownership & Delegated Administration 2.3 Cloud Storage Integrations & IAM Trust Policies 2.4 Identity Federation, SSO, SCIM & Authentication Policies
4 Chapter 3: Governance, Data Privacy, Network Security & Compliance
3.1 Column-Level Masking & Row Access Policies 3.2 Object Tagging, Tag-Based Masking & Audit Governance 3.3 Encryption, Key Management & Tri-Secret Secure 3.4 Aggregation Policies, Projection Policies & External Tokenization 3.5 Network Policies, Network Rules, External Access & Private Connectivity 3.6 Snowflake Editions & Compliance Architecture (PCI DSS, PII & PHI)
5 Chapter 4: Data Modeling in Snowflake
4.1 Dimensional Modeling: Star vs. Snowflake Schemas 4.2 Data Vault 2.0 Architecture in Snowflake 4.3 Relational Constraints & Query Optimizer Integration
6 Chapter 5: Data Sharing & Collaboration Solutions
5.1 Direct Data Sharing Architecture & Security 5.2 Managed Reader Accounts for External Consumers 5.3 Snowflake Marketplace, Data Exchange & Clean Rooms
7 Chapter 6: Multi-Cloud, Multi-Region & Business Continuity
6.1 Database & Account Replication Mechanics 6.2 Disaster Recovery Architecture & Client Redirect 6.3 Cross-Cloud Auto-Fulfillment & Listing Replication 6.4 Data Protection: Time Travel, Fail-safe & Storage Costs
8 Chapter 7: Environments, Lakehouse, DevOps & AI/ML Applications
7.1 Multi-Tier Environment Strategy & Zero-Copy Cloning 7.2 Data Lakehouse Architecture & Apache Iceberg 7.3 DataOps, CI/CD & Snowflake Git Integration 7.4 AI/ML Pipelines & Applications: Cortex AI, ML Functions, Snowpark Container Services, Streamlit & Native Apps
9 Chapter 8: Data Ingestion Architecture
8.1 Bulk Ingestion Architecture: COPY INTO Optimization 8.2 Snowpipe Continuous Automated Ingestion 8.3 Snowpipe Streaming & Real-Time Ingestion 8.4 Data Unloading Architecture & Cloud Export Patterns 8.5 Schema Detection, Schema Evolution & Source-Change Architecture
10 Chapter 9: Continuous Pipelines & Stream Transformation
9.1 Change Data Capture (CDC) with Snowflake Streams 9.2 Task Orchestration, DAGs & Serverless Scheduling 9.3 Declarative Data Pipelines with Dynamic Tables 9.4 Views, Materialized Views & Transformation Table Design
11 Chapter 10: Semi-Structured Data & Ecosystem Tooling
10.1 Semi-Structured Data: VARIANT, OBJECT & ARRAY Processing 10.2 Snowflake Ecosystem Connectors, Drivers & SQL API 10.3 Snowpark, User-Defined Functions & Stored Procedures
12 Chapter 11: Virtual Warehouse Architecture & Concurrency
11.1 Virtual Warehouse Architecture, Sizing & Credit Economics 11.2 Multi-Cluster Warehouses & Concurrency Scaling Policies 11.3 Warehouse Types & Query Acceleration Service
13 Chapter 12: Query Profiling & Performance Diagnostics
12.1 Query Profile Deep-Dive & Bottleneck Analysis 12.2 Memory Spilling, Warehouse Queuing & Timeout Governance 12.3 Three-Tier Caching Architecture & Result Reuse
14 Chapter 13: Storage Optimization, Cost Governance & Observability
13.1 Micro-Partitioning & Automatic Clustering 13.2 Search Optimization Service (SOS) & Point Lookup Acceleration 13.3 Resource Monitors, Financial Governance & Usage Observability 13.4 Warehouse Monitoring, Alerts, Event Tables & Performance Explorer
13.4 Warehouse Monitoring, Alerts, Event Tables & Performance Explorer
Key Takeaways Explain This Topic AI
WAREHOUSE_LOAD_HISTORY (AVG_RUNNING, AVG_QUEUED_LOAD, AVG_QUEUED_PROVISIONING, AVG_BLOCKED) and WAREHOUSE_EVENTS_HISTORY (resumes, suspensions, resizes, cluster changes) show whether a warehouse is overloaded, cold, or oversized.
Alerts evaluate a SQL condition on a schedule or on new data and run an action such as SYSTEM$SEND_EMAIL; they are created suspended, need EXECUTE ALERT (granted by ACCOUNTADMIN), and can run serverless (EXECUTE MANAGED ALERT) or on a named warehouse.
Notification integrations deliver messages by email, to cloud queues (Amazon SNS, Azure Event Grid, Google Cloud Pub/Sub), or to webhooks such as Slack, Microsoft Teams, or PagerDuty.
Event tables collect logs, traces, and metrics from procedures, UDFs, services, tasks, and dynamic tables; SNOWFLAKE.TELEMETRY.EVENTS is the default, and LOG_LEVEL, TRACE_LEVEL, and METRIC_LEVEL control what is captured.
Performance Explorer (Snowsight » Monitoring) charts query activity, warehouse changes, and table changes over time to find what changed and where to focus optimization.
Last updated: September 2026
Monitoring Sources: Which One Answers Which Question?
Question Best source Notes
Is a warehouse overloaded or waiting on provisioning? WAREHOUSE_LOAD_HISTORY (Account Usage view or Information Schema table function) AVG_RUNNING , AVG_QUEUED_LOAD , AVG_QUEUED_PROVISIONING , AVG_BLOCKED in 5-minute intervals
When did a warehouse resume, suspend, resize, or add clusters? WAREHOUSE_EVENTS_HISTORY Explains cold caches and provisioning waits
Which queries were slow, spilled, or queued? QUERY_HISTORY Account Usage: 1 year, ~45 min latency; Information Schema: 7 days, near real time
What did credits go to? WAREHOUSE_METERING_HISTORY , METERING_HISTORY Serverless services appear by SERVICE_TYPE
How well are tables pruned or clustered? Query Profile, SYSTEM$CLUSTERING_INFORMATION , TABLE_PRUNING_HISTORY Pair with 13.1
Account Usage vs. Information Schema (exam favorite): SNOWFLAKE.ACCOUNT_USAGE views include dropped objects, keep one year of history, and have latency of 45 minutes to 3 hours depending on the view. INFORMATION_SCHEMA views and table functions have no latency but shorter retention ( 7 days to 6 months depending on the function) and are scoped to one database. -- Is BI_WH saturated (queued load) or cold (queued provisioning)?
- SELECT start_time, avg_running, avg_queued_load, avg_queued_provisioning, avg_blocked
- FROM TABLE(INFORMATION_SCHEMA.WAREHOUSE_LOAD_HISTORY(
- DATE_RANGE_START => DATEADD('hour', -8, CURRENT_TIMESTAMP()),
- WAREHOUSE_NAME => 'BI_WH'))
- ORDER BY start_time;
Interpretation:
Sustained AVG_QUEUED_LOAD > 0 → concurrency pressure: scale out (multi-cluster) or split workloads.
AVG_QUEUED_PROVISIONING > 0 around resumes → auto-suspend may be too aggressive for the workload's gaps.
AVG_RUNNING far below capacity for long periods → the warehouse may be oversized or its auto-suspend too long.
Alerts and Notifications
An alert is a schema-level object that runs a condition (a SQL statement, usually EXISTS (...) ) and, if it returns rows, runs an action : CREATE OR REPLACE ALERT ops.monitoring.long_queue_alert
- SCHEDULE = '5 minute' -- omit WAREHOUSE for a serverless alert
- IF (EXISTS (
- SELECT 1
- FROM TABLE(INFORMATION_SCHEMA.WAREHOUSE_LOAD_HISTORY(
- DATE_RANGE_START => DATEADD('minute', -10, CURRENT_TIMESTAMP()),
- WAREHOUSE_NAME => 'BI_WH'))
- WHERE avg_queued_load > 1))
- THEN
- CALL SYSTEM$SEND_EMAIL('ops_email_int', 'dba-team@example.com',
- 'BI_WH is queuing', 'Queued load > 1 in the last 10 minutes');
ALTER ALERT ops.monitoring.long_queue_alert RESUME; -- alerts are created suspended
Key facts:
Types: an alert on a schedule (every n minutes or a cron expression) evaluates existing data; an alert on new data evaluates only new rows in a table or view — for example, new ERROR rows in the event table.
Compute: serverless alerts (no WAREHOUSE , requires EXECUTE MANAGED ALERT ; scales up to the equivalent of XXLARGE) or a specified warehouse (requires USAGE on it).
Privileges: EXECUTE ALERT on the account (grantable only by ACCOUNTADMIN ) plus CREATE ALERT on the schema.
Operations: ALERT_HISTORY shows runs; SUSPEND_ALERT_AFTER_NUM_FAILURES auto-suspends failing alerts.
Notification integrations define where messages go: TYPE = EMAIL (for SYSTEM$SEND_EMAIL ), TYPE = QUEUE for outbound messages to Amazon SNS, Azure Event Grid, or Google Cloud Pub/Sub , and TYPE = WEBHOOK for Slack, Microsoft Teams, or PagerDuty . The same integrations serve task error notifications, budgets, and alerts.
Event Tables: Logging, Tracing, and Metrics
An event table is a special table with a predefined schema that stores telemetry emitted by Snowflake objects:
Logs from stored procedures and UDF handlers (Python, Java, Scala, JavaScript, Snowflake Scripting).
Traces (spans and events) that show the flow and timing of code.
Metrics , plus events from Snowpark Container Services , Native Apps , tasks , and dynamic table refreshes.
Setup and control:
Snowflake provides a default event table, SNOWFLAKE.TELEMETRY.EVENTS , which is active unless you set another; a predefined view, SNOWFLAKE.TELEMETRY.EVENTS_VIEW , can be secured with a row access policy for broader access.
You can create your own with CREATE EVENT TABLE and activate it with ALTER ACCOUNT SET EVENT_TABLE = db.schema.events; . Associating an event table with a specific database is an Enterprise Edition feature.
Telemetry levels decide what is captured: LOG_LEVEL (for example ERROR , WARN , INFO ), TRACE_LEVEL , and METRIC_LEVEL , settable at account, database, schema, or object level.
Collecting telemetry has a cost, so capture detail where you need it (for example INFO in development, ERROR in production). ALTER PROCEDURE etl.procs.load_orders(VARCHAR) SET LOG_LEVEL = 'WARN';
- SELECT timestamp, record['severity_text']::STRING AS severity, value::STRING AS message
- FROM snowflake.telemetry.events_view
- WHERE resource_attributes['snow.executable.name']::STRING ILIKE 'LOAD_ORDERS%'
- AND record_type = 'LOG'
- ORDER BY timestamp DESC;
Combine event tables with an alert on new data to page the on-call engineer whenever a pipeline logs an ERROR , instead of waiting for users to notice missing data.
Performance Explorer
Performance Explorer (Snowsight » Monitoring » Performance Explorer ) provides interactive charts of SQL workload health:
Overall activity — are queries succeeding, and can users get work done?
Change over time — what changed (query volume, warehouse settings, table changes) and when?
Hot spots — which warehouses, users, or tables deserve attention first?
It surfaces warehouse events and top tables with change events, filtered by the viewer's privileges (some sections need full access or the GOVERNANCE_VIEWER database role). Architects use it to connect a performance regression to a cause — for example, a warehouse resized down on Tuesday or a large table that started receiving heavy updates — before drilling into Query Profile.
Putting It Together: A Monitoring Runbook
Budgets and resource monitors catch spend anomalies (13.3).
Alerts watch warehouse load, failed tasks, stale streams, or data-quality conditions and notify through notification integrations.
Event tables hold the detailed logs and traces needed to debug procedures, apps, and services.
Performance Explorer and Query Profile explain why performance changed and guide fixes such as clustering, search optimization, QAS, or warehouse changes.