Basic statistics tracking #25

New issue

Open

opened 2022-10-29 14:11:26 +00:00 by emacsen · 5 comments

emacsen commented

2022-10-29 14:11:26 +00:00

(Migrated from gitlab.com)

AC should do some basic statistics tracking, such as:

How many events it saw
How many events it thought were S2S activities
How many were allow-listed
How many were tagged
How many were blocked

To do this efficiently, the best way is probably to store this information inside a set of Redis keys. They could be simple incrementing values with a reset, or they could be stored in N minute resolution intervals, such as 5 minutes.

With 5 minute intervals, that's 12 keys an hour, or 288 keys a day, which sounds like a lot, but could easily be made into a query that takes these values and does a reduction on them to get a sum, but also still retain the details.

AC should do some basic statistics tracking, such as: - How many events it saw - How many events it thought were S2S activities - How many were allow-listed - How many were tagged - How many were blocked To do this efficiently, the best way is probably to store this information inside a set of Redis keys. They could be simple incrementing values with a reset, or they could be stored in N minute resolution intervals, such as 5 minutes. With 5 minute intervals, that's 12 keys an hour, or 288 keys a day, which sounds like a lot, but could easily be made into a query that takes these values and does a reduction on them to get a sum, but also still retain the details.

emacsen commented

2022-10-29 14:22:24 +00:00

(Migrated from gitlab.com)

mentioned in issue #26

emacsen commented

2022-10-29 14:24:54 +00:00

(Migrated from gitlab.com)

mentioned in issue #27

CSDUMMI commented

2023-03-15 11:57:20 +00:00

(Migrated from gitlab.com)

created branch 25-basic-statistics-tracking to address this issue

created branch [`25-basic-statistics-tracking`](/babka_net/activitycolander/-/compare/main...25-basic-statistics-tracking) to address this issue

CSDUMMI commented

2023-03-15 11:58:40 +00:00

(Migrated from gitlab.com)

I'll create a branch AdminAPI both to gather this information and to make it available through a REST API.

I'll create a branch `AdminAPI` both to gather this information and to make it available through a REST API.

CSDUMMI commented

2023-03-15 12:02:13 +00:00

(Migrated from gitlab.com)

The information that should be gathered for the API includes:

Number of Activities received
Number of Activities marked block and spam and passed
Number of times a check returned a non-zero score
Average score of a check

3 and 4 are included for the purpose of analyzing the effectiveness of checks (removing those that are rarely or never triggered).

The information that should be gathered for the API includes: 1. Number of Activities received 2. Number of Activities marked `block` and `spam` and `passed` 3. Number of times a check returned a non-zero score 4. Average score of a check 3 and 4 are included for the purpose of analyzing the effectiveness of checks (removing those that are rarely or never triggered).