Insights

Key Assets
Tables and views with a calculated Importance Score (based on # dependencies, avg. reads/writes, users, and more). The lookback window for this insight is 30 days.
Use this to:

• Identify important tables to add custom monitors to
• Communicate table/view usage to stakeholders
• Prioritise datasets for refactoring or migrations

Coverage Overview
Active monitors that Monte Carlo is applying to your data, including all out-of-the-box and advanced monitors.
Use this to:

• Quantify MC monitor coverage across schemas and tables
• Report increase in custom monitor adoption over time

Table Cleanup Suggestions
Dormant tables and views with no recent query activity
Use this to:

• Reduce storage costs by deleting unused tables
• Deprioritize unused datasets and tables during migrations

Field-level Cleanup Suggestions
Dormant fields with no recent query activity.
Use this to:

• Prioritize which tables are most ripe for cleanup
• Simplify tables by removing unused fields

Events
Details for all anomalies and schema changes detected by Monte Carlo, which then get grouped together into incidents. The lookback window for this insight is 90 days.
Use this to:

• Understand the threshold for what triggered an anomaly
• See which tables or views are consistently changing or unreliable

Table Read/Write Activity
Table read and write counts by day/week/month for each table in your data warehouse or data lake.
Use this to:

• Aggregate read/write query activity by schema, teams or other filter
• Gauge importance and prioritise development on tables with the highest read/write activity

Incident Query Changes
Shows changes in query patterns that may have led to an Incident on a table. Includes Incidents for the past two weeks and has a 36 hour delay.
Use this to:

• Identify if an Incident was caused by a new or updated query
• Identify if an Incident was caused by a recurring query that ceased

Deteriorating Queries
Queries displaying a consistent increase in execution runtime over the past 30 days. This insight will be available only if Monte Carlo detects anomalies in query runtime.
Use this to:

• Prevent data downtime by identifying queries that are at risk of timing out
• Optimise queries that are not scaling well
• Reduce cost by editing queries with increasing compute time

Rule and SLI Results
Log of query outputs and pass/breach results for SQL Rules and SLIs for the past 90 days
Use this to:

• Track progress towards SLAs or SLOs by aggregating SLI results over time
• Fine-tune Rules by understanding Rule results over time

Dimension Tracking Suggestions
Top 500 field recommendations for Dimension Tracking monitors, based on Table Importance Score (see Key Assets) and by using NLP on field names.
Use this to:

• Identify fields for Dimension Tracking monitors

Field Health Suggestions
Top 100 table recommendations for Field Health monitors, based on Table Importance Score (see Key Assets). Note that we exclude external tables as they tend to consume more compute.
Use this to:

• Identify tables for Field Health monitors

Misconfigured Monitors
Custom monitors (e.g. Field Health) that were configured in a way that won't result in meaningful anomaly detection, along with suggestions on how to fix them.
Use this to:

• Ensure custom monitors are working as intended
• Clean up outdated custom monitors

BI Dashboard Analytics
Usage data for Looker dashboards such as totals views and days since last view.
Use this to:

• See which dashboards are safe to deprecate or delete
• Prioritise heavily used dashboards in a migration

Incident History
All incidents detected by Monte Carlo over the last 6 months. The lookback window for this insight is 1 year.
Use this to:

• Report on the statuses of your Incidents
• Calculate Incident Response Rate and Time to First Response
• See trends in your anomalies and schema changes

Heavy Queries
Queries from the last week with the longest runtime and most bytes scanned. The top 5 queries are shown for each warehouse and executor.
Use this to:

• Find and optimise queries that are causing performance issues or stressing resources.
• Identify irresponsible query behaviour