Skip to content

Added additional env vars to control the frequency of detector activating#33

Open
symstu-tempesta wants to merge 2 commits into
mainfrom
25-new-env-vars
Open

Added additional env vars to control the frequency of detector activating#33
symstu-tempesta wants to merge 2 commits into
mainfrom
25-new-env-vars

Conversation

@symstu-tempesta

Copy link
Copy Markdown
Contributor

No description provided.

@symstu-tempesta symstu-tempesta force-pushed the 25-new-env-vars branch 2 times, most recently from cc26605 to aca57a6 Compare May 25, 2026 13:18

@krizhanovsky krizhanovsky left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a couple of comments, where I think we should do different things

Comment thread utils/access_log.py
" tfh UInt64,"
" dropped_events UInt64"
") ENGINE = MergeTree() ORDER BY timestamp"
)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should raise (log) and error and exit in case if there is no such table. tfw_logger creates the database and we'll have hard times to synchronize the table formats and also this might open an opportunity for hard races, when both the daemons start.

Comment thread example.env
@@ -68,6 +68,11 @@ BLOCKING_TYPES=["tft"]
# users should be fetched for the period 2025-01-01 00:00:00 to 2025-01-01 00:00:10
BLOCKING_WINDOW_DURATION_SEC=10

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, so no BLOCKING_WINDOW_DURATION_SEC defines the history period, i.e. if it is 10 seconds, then the history is at (-20, -10]. In #25 it makes sense to configure say, (-4200, -600] - we need a second option for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants