Revert PR #32 — VIN decode PostHog enrichment was duplicating query_logs #33

root · 2026-05-18T11:04:26+03:00

root commented

2026-05-18 11:04:26 +03:00

Reason: every prop in the new events already lives in query_logs.timings + scalar columns; panel reads via RO instead.

root added 1 commit 2026-05-18 11:04:27 +03:00

Revert "feat(telemetry): enrich VIN decode events for Süper Panel observability"

QA Gate (P0/P1) / Test affected app (pull_request) Has been cancelled

Details

0defbe7eb6

Reverts PR #32 (commit 0b1f033 / 4645c27).

Reason: the backend telemetry was duplicating data that already lives
in query_logs. Every field the new PostHog events carried — provider
chain, response_time_ms, success/error, cache_source, pl24_circuit_open,
brandId, aborted, partial_result — is captured per-row in:

  query_logs { userId, vin, brandId, source, success, errorMessage,
               responseTimeMs, timings (jsonb), createdAt }

Süper Panel already has read-only access to the Sase.tr Postgres via
DATABASE_URL_SASE_RO; the VIN Decode Observability Module (SP-VIN-001)
will read query_logs directly. PostHog hop adds latency (5min poll),
event-volume cost, KVKK weight (even sanitized VINs leaving the
service), and architectural duplication for zero observability gain.

Frontend PostHog events (vin_decode_candidates, candidate_selected,
search_input_validation_failed, vin_decode_retry_clicked) stay — those
are user-interaction signals query_logs doesn't capture.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

root merged commit 2497d326cd into main

2026-05-18 11:04:29 +03:00

root referenced this issue from a commit

2026-05-18 11:04:30 +03:00

Merge pull request 'Revert PR #32 — VIN decode PostHog enrichment was duplicating query_logs' (#33) from dev into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: root/sase.tr#33