Labels Milestones

New Issue

detection runner: persistance of the last detection #16

Open

opened 3 years ago by glitch4347 · 0 comments

glitch4347 commented 3 years ago (Migrated from github.com)

Owner

When runner starts, it needs to know from where detect launch analytic unit. I propose to save last detection timestamp

When runner starts, it needs to know from where detect launch analytic unit. I propose to save last detection timestamp

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

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview

Loading…

Cancel

Save

There is no content yet.