Event freshness anomalies
elementary.event_freshness_anomalies
elementary.event_freshness_anomalies
Monitors the freshness of event data over time, as the expected time it takes each event to load - that is, the time between when the event actually occurs (the event timestamp
), and when it is loaded to the database (the update timestamp
).
This test compliments the freshness_anomalies
test and is primarily intended for data that is updated in a continuous / streaming fashion.
The test can work in a couple of modes:
If only an
event_timestamp_column
is supplied, the test measures over time the difference between the current timestamp (“now”) and the most recent event timestamp.If both an
event_timestamp_column
and anupdate_timestamp_column
are provided, the test will measure over time the difference between these two columns.
Test configuration
Required configuration: event_timestamp_column
Default configuration: anomaly_direction: spike
to alert only on delays.
Last updated