Read-Only Warehouse Review
Warehouse investigations should start broad and aggregate, then narrow only when needed.
Allowed Source
Section titled “Allowed Source”snowflake://analytics_prodAggregate First
Section titled “Aggregate First”onequery query exec \ --source snowflake://analytics_prod \ --sql "select event_name, count(*) as events from analytics.events where event_date >= current_date - 7 group by event_name order by events desc limit 20"Narrow by Time Window
Section titled “Narrow by Time Window”onequery query exec \ --source snowflake://analytics_prod \ --sql "select date_trunc('hour', occurred_at) as hour, count(*) as failures from analytics.events where event_name = 'checkout_failed' and occurred_at >= current_timestamp - interval '24 hours' group by 1 order by 1"Review Rules
Section titled “Review Rules”- Do not start with raw event dumps.
- Keep time windows explicit.
- Preserve the source identifier in the analysis.
- Use a read-only warehouse role.
- Prefer saved views for sensitive data.
Result Note
Section titled “Result Note”Source: snowflake://analytics_prodWindow: last 24 hoursFinding: checkout_failed increased after 14:00 UTC, concentrated in payment_method='card'.Follow-up: compare deployment and provider incident timelines.