feat: log search field request_id && conversion_path display

[seefs001]

Summary by CodeRabbit

• New Features
  • Added a Request ID filter to the Usage Logs UI so you can search and filter log entries by Request ID.
  • Logging now records and surfaces a Request ID with each relevant log entry, improving traceability and making it easier to correlate logs to external requests.

[coderabbitai]

Walkthrough

Adds request ID support across logging: frontend filter and query param, controller reads request_id and forwards it, and model stores/filters logs by a new RequestId field.

Changes

Cohort / File(s)	Summary
Backend controller controller/log.go	Reads request_id query parameter and passes it to model log retrieval functions.
Backend model model/log.go	Adds RequestId string to Log; updates GetAllLogs(...) and GetUserLogs(...) signatures to accept requestId and filter by it; populates RequestId when creating logs; removed request_conversion from formatted user output.
Frontend filters & data web/src/components/table/usage-logs/UsageLogsFilters.jsx, web/src/hooks/usage-logs/useUsageLogsData.jsx	Adds request_id form field and default value; includes request_id in API query params for admin/non-admin log endpoints; renders "Request ID" row when present in log items.

Sequence Diagram(s)

sequenceDiagram
  participant UI as "User / Browser"
  participant FE as "Frontend hook\n(useUsageLogsData)"
  participant API as "Controller\n(controller/log.go)"
  participant Model as "Model\n(model/log.go)"
  participant DB as "Database"

  UI->>FE: enter filters (including request_id)
  FE->>API: GET /logs?request_id=... (admin/non-admin endpoint)
  API->>Model: GetAllLogs/GetUserLogs(..., requestId)
  Model->>DB: SELECT ... WHERE logs.request_id = ? (if provided)
  DB-->>Model: rows
  Model-->>API: log list (with RequestId field)
  API-->>FE: JSON response
  FE-->>UI: render logs (show Request ID row when present)

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• feat: log shows request conversion #2703 — touched formatting of user logs and the admin-only request_conversion field in model/log.go.
• feat: endpoint type log #2038 — added/surfaced additional log fields in usage-logs UI/data flow (similar changes to frontend hooks and filters).

Poem

🐰 I hopped through forms and server lanes,
Carried tiny request-id reins,
From field to model, stored with care,
Now every log knows which path it bears. 🥕

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions 'request_id' field and 'conversion_path display', both of which are addressed in the changeset. The request_id feature is implemented across controller, model, and frontend components. However, the title references 'conversion_path display' which contradicts the actual changes—the code explicitly removed the conversion_path field from user logs output.	Update the title to accurately reflect the changes: 'feat: add request_id log search field' or similar, removing the misleading reference to conversion_path display which was actually removed.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}