Skip to content

Fix appName option and count billing events via dailyEvents#575

Open
Kuchizu wants to merge 4 commits into
masterfrom
perf/mongo-optimizations
Open

Fix appName option and count billing events via dailyEvents#575
Kuchizu wants to merge 4 commits into
masterfrom
perf/mongo-optimizations

Conversation

@Kuchizu

@Kuchizu Kuchizu commented Jul 3, 2026

Copy link
Copy Markdown
Member

Driver 3.x only accepts lowercase appname
Limiter now sums dailyEvents daily counters for full days and counts raw events/repetitions only for the partial day around lastChargeDate

Copilot AI 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.

Pull request overview

This PR updates Mongo connection options for driver 3.x compatibility and refines limiter billing-period event counting by combining raw event scans for the “boundary day” with dailyEvents per-day counters for subsequent days.

Changes:

  • Switch Mongo connection option from appName to appname for MongoDB driver 3.x compatibility.
  • Update limiter DbHelper.getEventsCountByProject to count the partial boundary day via raw events/repetitions collections and sum later days via dailyEvents.
  • Expand limiter DB helper tests to cover dailyEvents-based counting and boundary-day filtering.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
workers/limiter/tests/index.test.ts Aligns mocked event timestamps with the boundary-day counting model.
workers/limiter/tests/dbHelper.test.ts Adds dailyEvents mocking and new tests for boundary-day vs dailyEvents counting behavior.
workers/limiter/src/dbHelper.ts Implements hybrid counting logic: raw scan for boundary day + aggregated dailyEvents for later days.
lib/db/controller.ts Uses lowercase appname Mongo option key for driver 3.x support.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 103 to +107
workspace?: WorkspaceDBScheme,
project: ProjectDBScheme,
eventsToMock: number
repetitionsToMock?: number,
dailyEventsToMock?: Array<{ groupingTimestamp: number; count: number }>,
Comment thread workers/limiter/src/dbHelper.ts
Comment thread workers/limiter/src/dbHelper.ts Outdated
@Kuchizu Kuchizu force-pushed the perf/mongo-optimizations branch from 68f49f6 to a7dcbb6 Compare July 8, 2026 08:32
Comment on lines +350 to +352
if (!this.shouldUseDailyEventsCounter(workspace._id.toString())) {
return this.dbHelper.getEventsCountByProjects(projects, since);
}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Lets compute both counters for such workspaces to be able to compare them.
The most useful way is to send logs to Telegram:

Workspace {name} event count:
Old algo: {old count}, took {time old}sec
New algo: {new count}, took {time new}sec

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