feat(usage-report): add per-sdk logs counters for web and ruby

[turnipdabeets]

Problem

logs_records_in_period in the org usage report has no SDK dimension, and the per-SDK split (get_teams_with_sdk_logs_records_in_period) only matched the mobile SDKs. Web and Ruby log volume was therefore not attributable, even though both SDKs now stamp telemetry.sdk.name on every record:

• posthog-js sets telemetry.sdk.name = "web"
• posthog-rails sets telemetry.sdk.name = "posthog-ruby" (see feat(rails): stamp telemetry.sdk.name on forwarded logs posthog-ruby#197)

The previous code comment said web was omitted because posthog-js "doesn't set telemetry.sdk.name yet" — that's no longer true.

Changes

Add web and ruby to the per-SDK logs split, mirroring the existing mobile pattern:

• SDK_TELEMETRY_NAMES: add "web": "web" and "posthog-ruby": "ruby" (and refresh the stale comment)
• UsageReportCounters: add web_logs_records_in_period, ruby_logs_records_in_period
• wire both through _get_all_usage_data and _get_team_report, plus the temporal multi_keys_mapping

The logs_distributed query itself is unchanged — this only widens the telemetry.sdk.name match list and adds the matching counters. (The earlier per-SDK PR was reverted once for querying the wrong table; this change deliberately doesn't touch the query.)

How did you test this code?

I'm an agent (Claude Code, human-directed). Automated only — no manual/product testing claimed.

Extended test_logs_per_sdk_usage_metrics to insert real web and posthog-ruby records into logs_distributed and assert the new counters (web=3, ruby=7), with a posthog-node / no-telemetry.sdk.name record staying uncounted. Ran locally against ClickHouse + Postgres:

• TestHogFunctionUsageReports::test_logs_per_sdk_usage_metrics — passed
• full TestHogFunctionUsageReports class — 6 passed

Regression caught: a new SDK that stamps telemetry.sdk.name would silently go uncounted (and a typo'd suffix would KeyError at report assembly) — the assertions on web/ruby counts cover both.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

Docs update

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

• Tool: Claude Code. Companion to feat(rails): stamp telemetry.sdk.name on forwarded logs posthog-ruby#197 (the posthog-rails side that stamps telemetry.sdk.name = "posthog-ruby").
• Decision: matched on telemetry.sdk.name (consistent with the mobile SDKs and feat(usage-report): re-add per-sdk logs counters via logs_distributed #60706) rather than telemetry.sdk.language / instrumentation_scope. The latter would work retroactively without an SDK release, but diverges from the established per-SDK convention; chose consistency.
• Scope check: confirmed test_aggregate_activity.py needs no change and the .ambr snapshot doesn't capture the per-SDK logs query, so neither required updates.
• No new ClickHouse query was added, so no migration/snapshot churn.

[greptile-apps]

_{Reviews (1): Last reviewed commit: "feat(usage-report): add per-sdk logs cou..." | Re-trigger Greptile}

[tests-posthog]

⏭️ Skipped snapshot commit because branch advanced to e35ec51 while workflow was testing 22ab5d9.

The new commit will trigger its own snapshot update workflow.

If you expected this workflow to succeed: This can happen due to concurrent commits. To get a fresh workflow run, either:

• Merge master into your branch, or
• Push an empty commit: git commit --allow-empty -m 'trigger CI' && git push

[pawel-cebula]

A couple of nit comments, approving it.

[marandaneto]

already some comments from billing otherwise lgtm

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-06-25 15:58 UTC	Run
prod-us	✅ Deployed	2026-06-25 16:20 UTC	Run
prod-eu	✅ Deployed	2026-06-25 16:52 UTC	Run