feat: track credits and latency in clickhouse by chronark · Pull Request #3854 · unkeyed/unkey

chronark · 2025-08-26T17:38:18Z

What does this PR do?

The main goal was to add credit tracking and add latencies, cause we need both in the dashboard.

This PR adds new raw tables for verifications and ratelimits to include the required columns and optimises the table settings.

This only adds tables, no code reads or writes to them yet, however there is a materialized view that populates the new table in real time.
I have already migrated our preview cluster and want to let it bake for a few days before migrating prod.

It also replaces the Goose migration system for ClickHouse with a Docker-based initialization approach. Instead of running migrations with Goose, the ClickHouse schema is now initialized directly during container startup using SQL files mounted into the container.

Key changes:

Created a custom ClickHouse Dockerfile that includes schema files
Added an initialization script that runs on container startup
Reorganized schema files into a more structured database-based layout
Added improved schema versions with better partitioning, TTL, and performance optimizations
Removed Goose dependencies from workflows and documentation
Updated Docker Compose configuration to use the new ClickHouse container

@perkinsjr for your PR we need to merge this one first, and then revert the schema changes in yours, then we should be good to go. I can do that if you want, lmk.

Type of change

Chore (refactoring code, technical debt, workflow improvements)
Enhancement (small improvements)

How should this be tested?

Start the local environment with make up and verify ClickHouse initializes correctly
Run integration tests to ensure ClickHouse functionality works as expected
Verify that the new schema structure is created properly in ClickHouse
Check that the migration documentation for v1 to v2 tables works as described

Checklist

Required

Summary by CodeRabbit

New Features
- Expanded analytics for verifications and rate limits: added latency (avg, p75, p99), spent credits, last-used tracking, and minute/hour/day/month aggregations.
Dev Experience
- Simplified local setup: ClickHouse is built with auto-initialization; separate migrator removed; easier startup.
Tests
- More reliable ClickHouse test startup with readiness wait; builds image before running tests.
Documentation
- Added zero-downtime migration guides; removed outdated ClickHouse test instructions.
Chores
- Streamlined CI by removing Goose steps; deprecated migration-related Makefile targets.

changeset-bot · 2025-08-26T17:38:23Z

⚠️ No Changeset found

Latest commit: 2f71831

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

coderabbitai · 2025-08-26T17:38:27Z

📝 Walkthrough

Walkthrough

Removes Goose-based ClickHouse migrations from CI, Makefiles, tooling, and tests. Introduces a custom ClickHouse image and init script that load SQL schemas at container startup. Replaces old migration files under internal/clickhouse with new schema files under go/pkg/clickhouse/schema. Adds v2 tables/materialized views for verifications and ratelimits.

Changes

Cohort / File(s)	Summary
CI workflows `.github/workflows/job_test_api_local.yaml`, `.github/workflows/job_test_unit.yaml`	Removed Goose install/migration steps; kept remaining steps unchanged.
Makefiles `Makefile`, `go/Makefile`	Deleted ClickHouse migration targets and retry loop for migrator; docker compose up no longer runs migrations.
Deployment: ClickHouse image and compose `deployment/Dockerfile.clickhouse`, `deployment/docker-compose.yaml`, `deployment/init-clickhouse.sh`	Added custom ClickHouse Dockerfile copying schemas and init script; compose now builds `clickhouse` from this Dockerfile; removed `clickhouse_migrator`; reformatted some commands; init script executes SQLs on first start.
Docs (testing and migrations) `apps/engineering/content/docs/contributing/testing.mdx`, `go/pkg/clickhouse/schema/databases/001_verifications/MIGRATION_v1_to_v2.md`, `.../002_ratelimits/MIGRATION_v1_to_v2.md`	Removed ClickHouse Tests/Goose docs; added migration guides for v1→v2 (verifications, ratelimits).
New ClickHouse schemas (verifications v2) `go/pkg/clickhouse/schema/databases/001_verifications/*.sql`	Added v2 raw table, per-minute/hour/day/month aggregate tables and MVs, temp sync MV from v1, and index on request_id.
New ClickHouse schemas (ratelimits v2) `go/pkg/clickhouse/schema/databases/002_ratelimits/*.sql`	Added v2 raw table with latency, per-minute/hour/day/month tables and MVs, last-used table/MV, temp sync MV from v1, and index on request_id.
Remove Goose-based migrations and image `internal/clickhouse/Dockerfile`, `internal/clickhouse/schema/*.sql`, `internal/clickhouse/schema/000_README.md`	Deleted Goose migrator Dockerfile and all Goose SQL migration files across metrics, verifications, ratelimits, business, billing.
Internal ClickHouse test utilities `internal/clickhouse/src/testutil.ts`, `internal/clickhouse/package.json`	Switched test container image to `unkey-clickhouse:latest`, added wait strategy and delay, removed Goose invocations; added script to build ClickHouse image; test script builds before running.
Local tooling `tools/local/src/main.ts`	Removed `clickhouse_migrator` from startup sets.
Minor formatting `go/pkg/db/retry.go`, `go/pkg/retry/retry_test.go`	Whitespace/alignment only; no behavioral changes.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Dev as Developer
  participant DC as docker-compose
  participant CH as ClickHouse (custom image)
  participant Init as init-clickhouse.sh
  participant FS as /opt/clickhouse-schemas

  Dev->>DC: docker compose up clickhouse
  DC->>CH: Build from deployment/Dockerfile.clickhouse
  CH->>Init: Run entrypoint init scripts on first start
  Init->>FS: Iterate database/* directories
  loop For each *.sql
    Init->>CH: clickhouse-client -q "<sql>"
    CH-->>Init: OK/ERR
  end
  Init-->>Dev: Initialization complete

sequenceDiagram
  autonumber
  actor CI as CI Workflow
  participant UT as Unit Tests
  participant API as API Local Tests

  CI->>UT: Setup Node / Build
  CI--X UT: Install goose (removed)
  CI->>UT: Run tests

  CI->>API: Build / Load MySQL schema
  CI--X API: Install goose (removed)
  CI--X API: goose up ClickHouse (removed)
  CI->>API: Run tests / dump & upload logs

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Possibly related PRs

feat: analytics api #2740 — Also modifies CI ClickHouse migration steps and related workflow YAML; overlaps with removal of Goose steps.
fix: do not send 4x as many rows to clickhouse #3161 — Refactors ClickHouse migration handling and test-time integration, aligning with replacing Goose and introducing embedded/init-based schemas.
feat: add minute granularity - This should be merged before key details #3240 — Updates ClickHouse timeseries schemas for verifications, overlapping with the new v2 tables/materialized views added here.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

📝 Generate Docstrings

🧪 Generate unit tests

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch 08-26-feat_track_credits_and_latency_in_clickhouse

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

Visit our Status Page to check the current availability of CodeRabbit.
Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

vercel · 2025-08-26T17:38:30Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
dashboard	Ready	Preview	Comment	Aug 26, 2025 5:47pm

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
engineering	Ignored	Preview		Aug 26, 2025 5:47pm

chronark · 2025-08-26T17:38:36Z

feat: track credits and latency in clickhouse #3854 👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

github-actions · 2025-08-26T17:44:20Z

Thank you for following the naming conventions for pull request titles! 🙏

graphite-app · 2025-08-26T17:45:12Z

Graphite Automations

"Notify author when CI fails" took an action on this PR • (08/26/25)

1 teammate was notified to this PR based on Andreas Thomas's automation.

perkinsjr

I don't see anything insane that would cause issues.

coderabbitai

Actionable comments posted: 62

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (6)

go/pkg/db/retry.go (2)
31-42: Optional: compute backoff instead of predefining slice (simpler, same semantics).

Removes the allocation and keeps behavior identical (50ms, 100ms, 200ms). Consider also adding jitter in the future to avoid synchronized retries, but that would require an extra import and is not necessary for this PR.
-    retry.Backoff(func(n int) time.Duration {
-      // Predefined backoff delays: 50ms, 100ms, 200ms
-      delays := []time.Duration{
-        DefaultBackoff,     // 50ms for attempt 1
-        DefaultBackoff * 2, // 100ms for attempt 2
-        DefaultBackoff * 4, // 200ms for attempt 3
-      }
-      if n <= 0 || n > len(delays) {
-        return DefaultBackoff // fallback to base delay
-      }
-      return delays[n-1]
-    }),
+    retry.Backoff(func(n int) time.Duration {
+      if n < 1 {
+        n = 1
+      }
+      // 50ms, 100ms, 200ms
+      return DefaultBackoff << (n - 1)
+    }),
43-56: Do not retry on context cancellation or deadline exceeded.

Currently, canceled or timed-out requests will still be retried, adding latency and wasting capacity. Skip retries for these cases.
     retry.ShouldRetry(func(err error) bool {
+      // Do not retry if the caller canceled or the context deadline elapsed.
+      if errors.Is(err, context.Canceled) || errors.Is(err, context.DeadlineExceeded) {
+        return false
+      }
       // Don't retry if resource is not found - this is a valid response
       if IsNotFound(err) {
         return false
       }
Add the necessary imports outside this hunk:
import (
  "context"
  "errors"
  "time"

  "github.com/unkeyed/unkey/go/pkg/retry"
)
go/pkg/retry/retry_test.go (1)
136-187: Optional: add boundary/limit cases to strengthen ShouldRetry coverage

Nice table-driven tests. Consider adding:

Attempts cap interaction with ShouldRetry (e.g., Attempts(2) + always-retry policy).

Zero-attempts behavior under ShouldRetry (mirror the “invalid attempts” case from TestRetry).

Apply this diff to extend the table with two focused cases:
@@
 	tests := []struct {
 		name          string
 		shouldRetry   func(error) bool
 		errorSequence []error
 		expectedCalls int
 		expectedError error
 		expectedSleep time.Duration
 	}{
+		// Attempts cap should stop even if ShouldRetry would continue
+		{
+			name: "attempts cap limits retries despite retryable errors",
+			shouldRetry: func(err error) bool { return true },
+			// two failures, then would succeed, but we will cap attempts to 2 below
+			errorSequence: []error{retryableError, retryableError, nil},
+			// we will set Attempts(2) for this case in the test body
+			expectedCalls: 2,
+			expectedError: retryableError,
+			expectedSleep: 100 * time.Millisecond,
+		},
+		// Zero attempts should short-circuit even with ShouldRetry policy
+		{
+			name: "zero attempts short-circuits even with ShouldRetry",
+			shouldRetry: func(err error) bool { return true },
+			errorSequence: []error{retryableError},
+			// we will set Attempts(0) for this case in the test body
+			expectedCalls: 0,
+			expectedError: errors.New("invalid attempts"), // will be replaced below
+			expectedSleep: 0,
+		},
 	{
 		name:          "should retry all errors by default",
 		shouldRetry:   nil, // default behavior
 		errorSequence: []error{retryableError, retryableError, nil},
 		expectedCalls: 3,
 		expectedError: nil,
 		expectedSleep: 300 * time.Millisecond, // 100ms + 200ms
 	},
@@
 	for _, tt := range tests {
 		t.Run(tt.name, func(t *testing.T) {
 			var retrier *retry
-			if tt.shouldRetry != nil {
-				retrier = New(ShouldRetry(tt.shouldRetry))
-			} else {
-				retrier = New()
-			}
+			// Per-test overrides for the two new boundary cases
+			switch tt.name {
+			case "attempts cap limits retries despite retryable errors":
+				retrier = New(ShouldRetry(tt.shouldRetry), Attempts(2))
+			case "zero attempts short-circuits even with ShouldRetry":
+				retrier = New(ShouldRetry(tt.shouldRetry), Attempts(0))
+				// err value asserted below; keep a stable sentinel
+				tt.expectedError = retrier.validate() // assume Do() returns validate() error
+			default:
+				if tt.shouldRetry != nil {
+					retrier = New(ShouldRetry(tt.shouldRetry))
+				} else {
+					retrier = New()
+				}
+			}
Note: If retry.validate() isn’t available, replace the sentinel with require.Error(t, err) and drop the equality check for that case. I can adjust to your actual constructor/validation behavior if you point me to the implementation.
go/pkg/clickhouse/schema/databases/001_verifications/004_key_verifications_per_minute_mv_v2.sql (1)

5-9: Verify target table schema aligns with GROUP BY keys and column list.

You project identity_id, key_id, tags into the sink. Confirm verifications.key_verifications_per_minute_v2 defines these columns and they are included in ORDER BY appropriately. High-cardinality keys (identity_id, key_id) at per-minute granularity can explode rows; confirm this matches dashboard needs.

Also applies to: 18-25
deployment/docker-compose.yaml (2)
114-138: Healthcheck should validate schema readiness, not just server liveness.

SELECT 1 returns OK even if init SQL hasn’t run yet. This can start dependents before tables exist.

Probe for a known table (e.g., ratelimits.raw_ratelimits_v2):
-          "--query",
-          "SELECT 1",
+          "--query",
+          "SELECT count() FROM system.tables WHERE database = 'ratelimits' AND name = 'raw_ratelimits_v2'",
This better gates service readiness for apiv2/agent.

290-295: Unused volume “clickhouse-keeper”.

No service mounts clickhouse-keeper. Dead volumes cause confusion.
 volumes:
   mysql:
   clickhouse:
-  clickhouse-keeper:
   s3:
   metald-aio-data:

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

💡 Knowledge Base configuration:

MCP integration is disabled by default for public repositories
Jira integration is disabled by default for public repositories
Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 041591d and 2f71831.

📒 Files selected for processing (88)

.github/workflows/job_test_api_local.yaml (0 hunks)
.github/workflows/job_test_unit.yaml (0 hunks)
Makefile (0 hunks)
apps/engineering/content/docs/contributing/testing.mdx (0 hunks)
deployment/Dockerfile.clickhouse (1 hunks)
deployment/docker-compose.yaml (4 hunks)
deployment/init-clickhouse.sh (1 hunks)
go/Makefile (0 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/002_raw_key_verifications_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/003_key_verifications_per_minute_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/004_key_verifications_per_minute_mv_v2.sql (3 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/005_key_verifications_per_hour_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/006_key_verifications_per_hour_mv_v2.sql (2 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/007_key_verifications_per_day_v4.sql (1 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/008_key_verifications_per_day_mv_v4.sql (1 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/009_key_verifications_per_month_v4.sql (1 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/010_key_verifications_per_month_mv_v4.sql (1 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/011_temp_sync_v1_to_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/001_verifications/MIGRATION_v1_to_v2.md (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/002_raw_ratelimits_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/003_ratelimits_per_minute_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/004_ratelimits_per_minute_mv_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/005_ratelimits_per_hour_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/006_ratelimits_per_hour_mv_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/007_ratelimits_per_day_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/008_ratelimits_per_day_mv_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/009_ratelimits_per_month_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/010_ratelimits_per_month_mv_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/011_ratelimits_last_used_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/012_ratelimits_last_used_mv_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/013_temp_sync_v1_to_v2.sql (1 hunks)
go/pkg/clickhouse/schema/databases/002_ratelimits/MIGRATION_v1_to_v2.md (1 hunks)
go/pkg/db/retry.go (1 hunks)
go/pkg/retry/retry_test.go (5 hunks)
internal/clickhouse/Dockerfile (0 hunks)
internal/clickhouse/package.json (1 hunks)
internal/clickhouse/schema/000_README.md (0 hunks)
internal/clickhouse/schema/001_create_databases.sql (0 hunks)
internal/clickhouse/schema/002_create_metrics_raw_api_requests_v1.sql (0 hunks)
internal/clickhouse/schema/003_create_verifications_raw_key_verifications_v1.sql (0 hunks)
internal/clickhouse/schema/004_create_verifications_key_verifications_per_hour_v1.sql (0 hunks)
internal/clickhouse/schema/005_create_verifications_key_verifications_per_day_v1.sql (0 hunks)
internal/clickhouse/schema/006_create_verifications_key_verifications_per_month_v1.sql (0 hunks)
internal/clickhouse/schema/007_create_verifications_key_verifications_per_hour_mv_v1.sql (0 hunks)
internal/clickhouse/schema/008_create_verifications_key_verifications_per_day_mv_v1.sql (0 hunks)
internal/clickhouse/schema/009_create_verifications_key_verifications_per_month_mv_v1.sql (0 hunks)
internal/clickhouse/schema/010_create_ratelimits_raw_ratelimits_table.sql (0 hunks)
internal/clickhouse/schema/011_create_telemetry_raw_sdks_v1.sql (0 hunks)
internal/clickhouse/schema/012_create_billing_billable_verifications_per_month_v1.sql (0 hunks)
internal/clickhouse/schema/013_create_billing_billable_verifications_per_month_mv_v1.sql (0 hunks)
internal/clickhouse/schema/014_create_ratelimits_ratelimits_per_minute_v1.sql (0 hunks)
internal/clickhouse/schema/015_create_ratelimits_ratelimits_per_hour_v1.sql (0 hunks)
internal/clickhouse/schema/016_create_ratelimits_ratelimits_per_day_v1.sql (0 hunks)
internal/clickhouse/schema/017_create_ratelimits_ratelimits_per_month_v1.sql (0 hunks)
internal/clickhouse/schema/018_create_ratelimits_ratelimits_per_minute_mv_v1.sql (0 hunks)
internal/clickhouse/schema/019_create_ratelimits_ratelimits_per_hour_mv_v1.sql (0 hunks)
internal/clickhouse/schema/020_create_ratelimits_ratelimits_per_day_mv_v1.sql (0 hunks)
internal/clickhouse/schema/021_create_ratelimits_ratelimits_per_month_mv_v1.sql (0 hunks)
internal/clickhouse/schema/022_create_business_active_workspaces_per_month_v1.sql (0 hunks)
internal/clickhouse/schema/023_create_business_active_workspaces_per_month_mv_v1.sql (0 hunks)
internal/clickhouse/schema/024_create_ratelimits_last_used_mv_v1.sql (0 hunks)
internal/clickhouse/schema/025_create_billable_verifications_v2.sql (0 hunks)
internal/clickhouse/schema/026_create_billable_ratelimits_v1.sql (0 hunks)
internal/clickhouse/schema/027_add_tags_to_verifications.raw_key_verifications_v1.sql (0 hunks)
internal/clickhouse/schema/028_create_verifications.key_verifications_per_hour_v2.sql (0 hunks)
internal/clickhouse/schema/030_create_verifications.key_verifications_per_day_v2.sql (0 hunks)
internal/clickhouse/schema/031_create_verifications.key_verifications_per_day_mv_v2.sql (0 hunks)
internal/clickhouse/schema/032_create_verifications.key_verifications_per_month_v2.sql (0 hunks)
internal/clickhouse/schema/033_create_verifications.key_verifications_per_month_mv_v2.sql (0 hunks)
internal/clickhouse/schema/034_billing_read_from_verifications.key_verifications_per_month_v2.sql (0 hunks)
internal/clickhouse/schema/035_business_update_active_workspaces_keys_per_month_mv_v1_read_from_verifications.key_verifications_per_month_v2.sql (0 hunks)
internal/clickhouse/schema/036_create_verifications.key_verifications_per_hour_v3.sql (0 hunks)
internal/clickhouse/schema/037_create_verifications.key_verifications_per_hour_mv_v3.sql (0 hunks)
internal/clickhouse/schema/038_create_verifications.key_verifications_per_day_v3.sql (0 hunks)
internal/clickhouse/schema/039_create_verifications.key_verifications_per_day_mv_v3.sql (0 hunks)
internal/clickhouse/schema/040_create_verifications.key_verifications_per_month_v3.sql (0 hunks)
internal/clickhouse/schema/041_create_verifications.key_verifications_per_month_mv_v3.sql (0 hunks)
internal/clickhouse/schema/042_create_api_requests_per_hour_v1.sql (0 hunks)
internal/clickhouse/schema/043_create_api_requests_per_hour_mv_v1.sql (0 hunks)
internal/clickhouse/schema/044_create_api_requests_per_minute_v1.sql (0 hunks)
internal/clickhouse/schema/045_create_api_requests_per_minute_mv_v1.sql (0 hunks)
internal/clickhouse/schema/046_create_api_requests_per_day_v1.sql (0 hunks)
internal/clickhouse/schema/047_create_api_requests_per_day_mv_v1.sql (0 hunks)
internal/clickhouse/schema/048_raw_ratelimits_metrics_indexes_v1.sql (0 hunks)
internal/clickhouse/schema/049_raw_api_metrics_ratelimit_indexes_v1.sql (0 hunks)
internal/clickhouse/schema/050_create_verifications.key_verifications_per_minute_v1.sql (0 hunks)
internal/clickhouse/src/testutil.ts (2 hunks)
tools/local/src/main.ts (1 hunks)

💤 Files with no reviewable changes (56)

apps/engineering/content/docs/contributing/testing.mdx
go/Makefile
internal/clickhouse/schema/022_create_business_active_workspaces_per_month_v1.sql
internal/clickhouse/schema/043_create_api_requests_per_hour_mv_v1.sql
internal/clickhouse/Dockerfile
internal/clickhouse/schema/026_create_billable_ratelimits_v1.sql
internal/clickhouse/schema/000_README.md
internal/clickhouse/schema/048_raw_ratelimits_metrics_indexes_v1.sql
.github/workflows/job_test_unit.yaml
internal/clickhouse/schema/021_create_ratelimits_ratelimits_per_month_mv_v1.sql
internal/clickhouse/schema/049_raw_api_metrics_ratelimit_indexes_v1.sql
internal/clickhouse/schema/001_create_databases.sql
internal/clickhouse/schema/023_create_business_active_workspaces_per_month_mv_v1.sql
internal/clickhouse/schema/045_create_api_requests_per_minute_mv_v1.sql
internal/clickhouse/schema/017_create_ratelimits_ratelimits_per_month_v1.sql
internal/clickhouse/schema/011_create_telemetry_raw_sdks_v1.sql
internal/clickhouse/schema/030_create_verifications.key_verifications_per_day_v2.sql
internal/clickhouse/schema/047_create_api_requests_per_day_mv_v1.sql
internal/clickhouse/schema/032_create_verifications.key_verifications_per_month_v2.sql
internal/clickhouse/schema/024_create_ratelimits_last_used_mv_v1.sql
internal/clickhouse/schema/040_create_verifications.key_verifications_per_month_v3.sql
internal/clickhouse/schema/038_create_verifications.key_verifications_per_day_v3.sql
internal/clickhouse/schema/027_add_tags_to_verifications.raw_key_verifications_v1.sql
internal/clickhouse/schema/041_create_verifications.key_verifications_per_month_mv_v3.sql
internal/clickhouse/schema/042_create_api_requests_per_hour_v1.sql
internal/clickhouse/schema/019_create_ratelimits_ratelimits_per_hour_mv_v1.sql
internal/clickhouse/schema/039_create_verifications.key_verifications_per_day_mv_v3.sql
internal/clickhouse/schema/034_billing_read_from_verifications.key_verifications_per_month_v2.sql
internal/clickhouse/schema/004_create_verifications_key_verifications_per_hour_v1.sql
internal/clickhouse/schema/046_create_api_requests_per_day_v1.sql
internal/clickhouse/schema/005_create_verifications_key_verifications_per_day_v1.sql
internal/clickhouse/schema/016_create_ratelimits_ratelimits_per_day_v1.sql
internal/clickhouse/schema/018_create_ratelimits_ratelimits_per_minute_mv_v1.sql
internal/clickhouse/schema/012_create_billing_billable_verifications_per_month_v1.sql
internal/clickhouse/schema/003_create_verifications_raw_key_verifications_v1.sql
internal/clickhouse/schema/044_create_api_requests_per_minute_v1.sql
internal/clickhouse/schema/014_create_ratelimits_ratelimits_per_minute_v1.sql
internal/clickhouse/schema/050_create_verifications.key_verifications_per_minute_v1.sql
internal/clickhouse/schema/031_create_verifications.key_verifications_per_day_mv_v2.sql
internal/clickhouse/schema/009_create_verifications_key_verifications_per_month_mv_v1.sql
internal/clickhouse/schema/010_create_ratelimits_raw_ratelimits_table.sql
internal/clickhouse/schema/028_create_verifications.key_verifications_per_hour_v2.sql
.github/workflows/job_test_api_local.yaml
internal/clickhouse/schema/036_create_verifications.key_verifications_per_hour_v3.sql
Makefile
internal/clickhouse/schema/033_create_verifications.key_verifications_per_month_mv_v2.sql
internal/clickhouse/schema/008_create_verifications_key_verifications_per_day_mv_v1.sql
internal/clickhouse/schema/015_create_ratelimits_ratelimits_per_hour_v1.sql
internal/clickhouse/schema/035_business_update_active_workspaces_keys_per_month_mv_v1_read_from_verifications.key_verifications_per_month_v2.sql
internal/clickhouse/schema/025_create_billable_verifications_v2.sql
internal/clickhouse/schema/037_create_verifications.key_verifications_per_hour_mv_v3.sql
internal/clickhouse/schema/020_create_ratelimits_ratelimits_per_day_mv_v1.sql
internal/clickhouse/schema/006_create_verifications_key_verifications_per_month_v1.sql
internal/clickhouse/schema/007_create_verifications_key_verifications_per_hour_mv_v1.sql
internal/clickhouse/schema/002_create_metrics_raw_api_requests_v1.sql
internal/clickhouse/schema/013_create_billing_billable_verifications_per_month_mv_v1.sql

🧰 Additional context used

📓 Path-based instructions (5)

**/*.go