hastic
/
hastic
4
1
Fork 0
Code Issues 61 Pull Requests Releases Activity
Labels Milestones
New Issue

null last detection case #56

Open
opened 3 years ago by glitch4347 · 2 comments
glitch4347 commented 3 years ago (Migrated from github.com)
Owner

When analytic unit is just created, then last_detection is null. So the question is froim which timestamp I should start detections when I start detection runner first time.
@rozetko what do you think?

When analytic unit is just created, then `last_detection` is null. So the question is froim which timestamp I should start detections when I start detection runner first time. @rozetko what do you think?
rozetko commented 3 years ago (Migrated from github.com)
Owner

@glitch4347
I think it'd be a good idea to split up detections into "historical" and "realtime" because non-separate detections have introduced a lot of development problems earlier

In this case, we can define some constant timerange (e.g. 30 minutes, or even configurable / dependent on datapoints interval) and start realtime detections from now-30m to now
Also, we can run historical detections only on a visible timerange

@glitch4347 I think it'd be a good idea to split up detections into "historical" and "realtime" because non-separate detections have introduced a lot of development problems earlier In this case, we can define some constant timerange (e.g. 30 minutes, or even configurable / dependent on datapoints interval) and start realtime detections from `now-30m` to `now` Also, we can run historical detections **only** on a visible timerange
glitch4347 commented 3 years ago (Migrated from github.com)
Owner

In this task should be implemented getting info about the last detection for the analytic unit

In this task should be implemented getting info about the last detection for the analytic unit
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
active-analytic-unit-#66
analytic-unit-type-and-meta-in-db-#65
anomly-detector-configurable-iteration-steps-#35
detection_runner_updade
env-variables-configuration-#55
env-vars-docs-#90
improve-anomaly-detector
main
master
seasonality-grid-#28
set-seasonality-with-mouse-#30
ui-not-editable-confidence-param-#99
Labels
Apply labels
Clear labels
bug
Something isn't working documentation
Improvements or additions to documentation duplicate
This issue or pull request already exists enhancement
New feature or request good first issue
Good for newcomers help wanted
Extra attention is needed invalid
This doesn't seem right question
Further information is requested refactoring wontfix
This will not be worked on
No Label bug documentation duplicate enhancement good first issue help wanted invalid question refactoring wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
0.0.1
Assignees
Assign users
Clear assignees
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(MISSING)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes