Let our Slack chatbot create the anomaly test you need.
This configuration controls the duration of the time buckets.
To calculate how data changes over time and detect issues, we split the data into consistent time buckets.
For example, if we use daily (period=day
, count=1
) time bucket and monitor for row count anomalies, we will count new rows per day.
Depending on the nature of your data, it may make sense to modify this parameter.
For example, if you want to detect volume anomalies in an hourly resolution, you should set the time bucket to period=hour
and count=1
.
time_bucket: {period: day, count: 1}
timestamp_column
time_bucket change impact
training_period
and detection_period
of the test might be extended to ensure full time buckets (for example, full week Sunday-Saturday).Let our Slack chatbot create the anomaly test you need.
This configuration controls the duration of the time buckets.
To calculate how data changes over time and detect issues, we split the data into consistent time buckets.
For example, if we use daily (period=day
, count=1
) time bucket and monitor for row count anomalies, we will count new rows per day.
Depending on the nature of your data, it may make sense to modify this parameter.
For example, if you want to detect volume anomalies in an hourly resolution, you should set the time bucket to period=hour
and count=1
.
time_bucket: {period: day, count: 1}
timestamp_column
time_bucket change impact
training_period
and detection_period
of the test might be extended to ensure full time buckets (for example, full week Sunday-Saturday).