Denys
10/10/2023, 12:56 PM- elementary.dimension_anomalies:
dimensions:
- <dimension_1>
- <dimension_2>
- <dimension_3>
min_training_set_size: 1
tags: ["elementary"]
backfill_days: 1
days_back: 1
config:
severity: warn
1. It's been more than 3 days but it 's still showing 'Not enough data to calculate anomaly score'. I remember it wasn't the case with volume anomalies - there it was showing the graph after one day with the same config. Do these tests work differently?
2. I need to create test(s) that would group by 3 columns SEPARATELY. This implies creating 3 different blocks of code, right? And the attached config makes elementary group by 3 columns at once?
3. When I artificially change row number (using LIMIT), I get a warning from elementary, but when I want to see some details, I see what's on the attached screenshot. Why aren't those fileds filled?Ella Katz
10/10/2023, 2:45 PMmin_training_set_size = 1 but you have 0 training set because your days_back equals your backfill_days (so your detection period is 1 and your training period is in fact 0). If you set up days_back=2 that'll match. but I will stress this is not a recommended setup, and using more days with a timestamp column is better and also has immediate results.
2. Exactly right
3. There's a bug in the latest version that causes the fields to be unpopulated. We're working on a fix, in the meantime you can see the details in the result description sectionDenys
10/11/2023, 6:39 AMDenys
10/17/2023, 7:13 AM- elementary.dimension_anomalies:
dimensions:
- device_online_status
min_training_set_size: 1
timestamp_column: updated_at
tags: ["elementary"]
backfill_days: 1
days_back: 21
config:
severity: warnElla Katz
10/17/2023, 7:36 AM--vars '{"force_metrics_backfill": true}'
?Denys
10/17/2023, 2:02 PMElla Katz
10/17/2023, 2:58 PMDenys
10/17/2023, 3:15 PMElla Katz
10/17/2023, 3:32 PMDenys
10/17/2023, 3:36 PMelementary:
+schema: "elementary"Ella Katz
10/17/2023, 3:37 PMElla Katz
10/17/2023, 3:37 PM