Events definitions

Events represent key observations about your data warehouse—like inefficient pipelines, critical schema changes, or cost anomalies. They are curated signals Alvin processes from raw activity to detect inefficiencies and address operational problems.

Events power Workflows, enabling you to act on observations. They’re the foundation of Alvin’s ability to turn warehouse activity into meaningful actions—the first step towards actionable insights and eventual resolution.

Working with Events

You can view the raw feed of all events on the Events tab.

However, their true value lies in setting up Workflows that allow you to automate responses, trigger alerts, and streamline operational processes based on events. See Workflows for more information.

List of all Events

This is a list of all events currently available to Alvin users. We’re continually refining it based on customer feedback and our understanding of what matters most in data warehouses.

anomaly detected

When a new anomaly was detected. Anomalies include unexpected spikes in cost or volume or quality issues such as freshness.

anomaly resolved

When an anomaly was resolved. Indicates that the anomaly’s root cause was addressed, and normal behavior resumed.

dbt low ROI

dbt model was detected as being low ROI. This means the model runs frequently but has minimal impact on data consumption.

dbt model reactivated

Model was used again after previously being considered stale. Typically occurs when downstream dependencies or queries start accessing the model again.

dbt model stale

A dbt model is considered stale after not being used for 30 days. A stale model can indicate redundancy, mismanagement, or unused data assets.

dbt test failed

When a dbt test ran with failures. Examples include failing row checks, unexpected null values, or constraint violations.

dbt test passed

When a dbt test ran successfully.

entity added

An entity was seen for the first time.

entity deleted

An entity disappeared from the system.

entity labels updated

An entity's labels have been modified (added, removed, or value changed).

entity reactivated

Entity was used again after previously being considered stale.

entity schema updated

An entity's schema has been modified (fields added, removed, or types changed). Schema updates can affect downstream workloads and should be monitored for compatibility issues.

entity stale

Entity is considered stale after 30 days.

full refresh detected

When a table with a full refresh materialization is executed. Based on the processed historical data. The full refresh can be classified into 4 values based on the upstream data:

• FULL_REFRESH_WITH_INCREMENTAL_UPSTREAM

• FULL_REFRESH_WITH_NO_UPSTREAM

• FULL_REFRESH_WITH_NO_INCREMENTAL_UPSTREAM

• INCREMENTAL_WITH_UPSTREAM

full refresh resolved

When a full refresh was resolved.

inefficient cluster config detected

Examples include unclustered large tables or tables clustered on low-impact columns. The BigQuery recommender uses the project's workload execution data from the past 30 days to analyze each BigQuery table for inefficient clustering configurations.

inefficient cluster config resolved

When an inefficient cluster config was resolved.

inefficient pricing model detected

The Alvin recommender uses the project's workload execution data from the past 30 days to analyze each workload for inefficient BigQuery pricing configurations, for example On-demand model instead of Enterprise or the other way around.

inefficient pricing model resolved

When an inefficient pricing model was resolved.

inefficient storage pricing model detected

The Alvin recommender uses the dataset table's storage data from the past 30 days to analyze each table for inefficient dataset storage configurations. Examples include using the logical storage model instead of physical or the other way around.

inefficient storage pricing model resolved

When an inefficient storage pricing model was resolved.

query insight detected

When a query insight is detected. Query insights highlight inefficiencies, redundant operations, or optimization opportunities. They are generated by the Alvin parser or integrated external tools.

query insight resolved

When a query insight is resolved. Indicates that the suggested query optimizations or insights were applied successfully.

unbalanced table build detected

Unbalanced table builds lead to suboptimal pipelines and increased costs. This typically happens when tables are updated more often than their source tables.

unbalanced table build resolved

When an unbalanced table build was resolved.

workload detected

A new workload is detected when a workload is run that didn't exist before.

workload failed

A workload ran with execution errors.