Skip to content

docs(billing): scope the usage_log workspace index note to created_at windows #9479

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
waleedlatif1 merged 2 commits into from
Oct 30, 2026
Merged

docs(billing): scope the usage_log workspace index note to created_at windows #9479

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4e94d28
docs(billing): scope the usage_log workspace index note to created_at…
waleedlatif1 Oct 30, 2026
c3f498f
docs(billing): limit the workspace index note to the reads it covers
waleedlatif1 Oct 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions apps/sim/lib/billing/core/usage-analytics-queries.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,11 @@ import type { DbClient } from '@/lib/db/types'
* and the member/source breakdowns are index-only. `workspace_id`, `workflow_id`,
* `description`, `metadata`, and `execution_id` are NOT in it, so the remaining
* reads heap-fetch per row — which is why they are issued only for the dimension
* actually being viewed. A read narrowed to one workspace runs on
* `usage_log_workspace_created_at_cost_idx` instead, which also covers `workflow_id`.
* actually being viewed. Narrowed to one workspace over a `created_at` window (a range
* or a reporting period), the totals, the series, and the member, source and workflow
* breakdowns are index-only on `usage_log_workspace_created_at_cost_idx` instead, which
* also covers `workspace_id` and `workflow_id`; the model breakdowns still heap-fetch,
* and a Stripe-period drill-down matches the period stamps, which that index lacks.
*/

export interface UsageTimeSeriesRow {
Expand Down