To configure Elementary OSS to use a specific timestamp column for anomaly detection and monitoring, you should set the timestamp column under the elementary config in your model’s YAML file, as you have done:

yaml models:   - name: L1__client_events     config:       materialized: incremental       incremental_strategy: append       event_time: created_at       begin: 2025-05-01       batch_size: day       time_interval: hour       elementary:         timestamp_column: created_at

The key parameter for Elementary is

elementary.timestamp_column

. This tells Elementary which column to use for time-bucketing and anomaly detection. The

event_time

parameter is not used by Elementary; it is likely used by your own dbt model logic or another tool. If you want Elementary to use only the

event_time

column, you should set:

yaml elementary:   timestamp_column: event_time

However, based on your example, it looks like your event time is already stored in the

created_at

column, and you have set

elementary.timestamp_column: created_at

, which is correct for Elementary. If you want to remove the

created_at

reference and use only

event_time

, you must ensure that the column

event_time

exists in your model and then update the config:

yaml elementary:   timestamp_column: event_time

Summary: - Elementary uses the column specified in

elementary.timestamp_column

for its time-based anomaly detection. - You can remove the

created_at

reference and use only

event_time

if that is your desired timestamp column, as long as it exists in your model. - The other parameters (

event_time

,

begin

, etc.) are not used by Elementary for anomaly detection. For more details, see the official documentation on the

timestamp_column

configuration: [Elementary Docs: timestamp_column](https://docs.elementary-data.com/data-tests/anomaly-detection-configuration/timestamp-column). If you have further requirements or want to use a SQL expression or a different column, Elementary supports specifying the column name directly, and recent versions allow more flexibility with SQL expressions as well, depending on your version and setup. If you encounter issues, please specify your Elementary version and the exact error or behavior you see.