3 ms·
Gitlab also has this: https://gitlab.com/gitlab-com/gl-infra/tamland https://gitlab.com/gitlab-com/gl-infra/tamland I'm not really smart in these areas, but it
by CubsFan1060 2y ago
Gitlab also has this: https://gitlab.com/gitlab-com/gl-infra/tamland https://gitlab.com/gitlab-com/gl-infra/tamland
I'm not really smart in these areas, but it feels like forecasting and anomaly detection are pretty related. I could be wrong though.
- diab0lic 2y agoYou are not wrong! An entire subclass of anomaly detection can basically be reduced to: forecast the next data point and then measure the forecast error when the data point arrives.
- deleted 2y ago[deleted]
- fnordpiglet 2y agoWell it doesn’t really require a forecast - variance based anomaly detection doesn’t make an assertion of the next point but that its maximum change is within some band. Such models usually can’t be used to make a forecast other than the banding bounds.
- diab0lic 2y agoThat would be a different subclass of anomaly detection solutions.
- fraserphysics 2y agoIf you need to detect anomalies as soon as they occur, that seems right. But if you want to detect them later you can also combine back-casting with forecasting. Like Kalman smoothing.