Date: 2026-03-11 Severity: High — core user interactions broken on production web app Time to Resolution: ~6 hours of investigation

Epic: TVM-1698 Date: 2026-02-02 Author: Raymond Mintz

Complete guide for setting up and using the ClickUp CLI on Ubuntu Linux.

• Node.js and npm installed
• ClickUp account with API access
• jq installed for JSON processing: sudo apt install jq

Problem: ClickHouse consumer stuck since 1/27, massive lag preventing event ingestion

Root Cause: 4 bad test messages blocking consumer across all 3 Kafka partitions:

• Partition 0, Offset 58: {"test":"connection_test",...}
• Partition 1, Offset 56: {"test":"direct_publish",...}
• Partition 2, Offset 113: {"test":"message",...}

Development:

POST https://playtv-api.forte.ws/v1/events

Production: (coming soon)

Here’s a concise summary + work items focused on implementation‑relevant points from the Kafka meeting notes.

Summary (implementation‑relevant highlights)

• The events endpoint currently requires auth, but there’s consensus that unauthenticated (guest) events are needed. This is a potential DDoS vector, so any unauthenticated mode needs rate‑limiting or an API key strategy.
• Clients were hitting 500s on the events endpoint. Root cause likely in validation/headers. Once the correct request + headers were used, responses became sane (401 or validation errors). Accept header absence can trigger HTML response instead of JSON.
• Logging quality is important for debugging bad payloads; logs should be useful in dev.
• Feature flag is required on mobile/web so event sending can be toggled off by default, especially in production builds.
• Batching events is expected; payloads should accept arrays and clients can send every 5–10 seconds.
• Brand/tenant identification s

1. Send Yan the metrics endpoint and payload (explicitly requested)

   • Endpoint already exists at POST /v1/events (no /api prefix)
   • Controller: app/Http/Controllers/EventController.php
   • Returns 202 {"success": true}

2. Increase payload size limit - Support batch events (~500KB suggested)

This is the JSON structure for all events published to Kafka topics (events.raw, events.views).

{
  "metadata": {
    "event_id": "uuid-v7",

• Device: /dev/md0
• Type: RAID1 (mirror)
• Size: 8TB (2x 8TB drives)
• Mount: /mnt/storage