Rollup duplicate high-volume event logs into a single row instead of deleting duplicates
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 44/100
Research direction
Start at app/workers/prune_event_logs_worker.rb around line 73, where duplicate high-volume event logs are currently pruned, and read the EventLog model and its schema to see what a rolled-up row could store. Expect a migration to add a count (and possibly a timestamps array) plus updated worker logic, with existing worker tests under test/ to extend. The issue leaves the shape of the rollup open (count vs. timestamp array), so agree on that before starting; done means duplicates collapse into one row carrying how many times the event fired that day.
Written by the indexing model from the issue text.
Description
Currently, we prune duplicate event logs for certain high-volume events. Instead, we should rollup the duplicates into a single row so that we don't lose history. It may be valuable information to some to see that a license was validated n times on a certain day, or that a machine sent n heartbeat pings on a certain day. But right now, we lose that information because duplicates are pruned rather than rolled up, so only 1 event log is saved per-day.
Keeping a simple count should be sufficient. But we should also consider keeping an array of timestamps as well.
- Dominant language
- Gherkin
- Stars
- 1.6k
- Forks
- 131
- Avg merge
- 13h 52m
- Merged PRs (30d)
- 9
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from keygen-sh/keygen-api
-
bug detail
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
keygen-sh/keygen-api#1161 ·
Maintainers usually reply within 1 day
-
bug detail
Difficulty 4/5 3-5 days Newbie friendliness 45/100
keygen-sh/keygen-api#1162 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
keygen-sh/keygen-api#1148 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
keygen-sh/keygen-api#1137 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
keygen-sh/keygen-api#1134 ·
Maintainers usually reply within 1 day
All issues in keygen-sh/keygen-api
Similar issues
-
[Bug] method_logger uses fragile definition-time inspect stack frame instead of func.__qualname__Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area:io area:warnings bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
fglock/PerlOnJava#2024 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Codeinwp/themeisle-companion#1013 ·
Maintainers usually reply within 1 day
-
Team:ResponseOps technical debt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
elastic/kibana#304569 · 1 comment ·
Maintainers usually reply within 1 day
-
area:qmc bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 3 days