feat: add "View logs" menu item to customer, team, and virtual key tables

[impoiler]

Summary

Adds a "View logs" action to the dropdown menus in the Customers, Teams, and Virtual Keys tables. This allows users to quickly navigate to the logs page pre-filtered by the selected customer, team, or virtual key without having to manually configure filters.

Changes

• Added a "View logs" DropdownMenuItem to the CustomerActionsMenu that links to /workspace/logs with customer_ids pre-populated as a search param
• Added a "View logs" DropdownMenuItem to the TeamActionsMenu that links to /workspace/logs with team_ids pre-populated as a search param
• Added a "View logs" DropdownMenuItem to the VKActionsMenu that links to /workspace/logs with virtual_key_ids pre-populated as a search param
• Used Link from @tanstack/react-router rendered via asChild to ensure proper client-side navigation while maintaining dropdown item styling
• Added ScrollText icon from lucide-react to visually distinguish the new action

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

1. Navigate to the Customers, Teams, or Virtual Keys table in the workspace
2. Open the actions dropdown (...) for any row
3. Click "View logs"
4. Verify you are redirected to /workspace/logs with the appropriate filter (customer_ids, team_ids, or virtual_key_ids) pre-applied for the selected entity

cd ui
pnpm i || npm i
pnpm build || npm run build

Screenshots/Recordings

Add before/after screenshots showing the new "View logs" option in the dropdown menus.

Breaking changes

• Yes
• No

Related issues

Security considerations

None. This change only adds navigation links using existing route and search param patterns. No new data is exposed.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

Summary by CodeRabbit

• New Features

  • Added "View logs" quick-access action to customer, team, and virtual key management tables. Users can navigate directly to activity logs with relevant filters pre-populated from the selected entity, streamlining audit trail access and investigations.

• Chores

  • Improved URL query/search handling to make filter and search parameter serialization more consistent when navigating and sharing links.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2ccd6703-8791-40a8-a57d-e8207f9c13cd

📥 Commits

Reviewing files that changed from the base of the PR and between e9ef1b2 and 390d19e.

📒 Files selected for processing (4)

• ui/app/main.tsx
• ui/app/workspace/governance/views/customerTable.tsx
• ui/app/workspace/governance/views/teamsTable.tsx
• ui/app/workspace/virtual-keys/views/virtualKeysTable.tsx

---

📝 Walkthrough

Walkthrough

Router adds a custom stringifySearch that serializes arrays as comma-separated values; customer, team, and virtual-key action menus add "View logs" links to /workspace/logs that pass the selected entity IDs as search params and close the dropdown on click.

Changes

Logs Navigation and Query Serialization

Layer / File(s)	Summary
Router search serialization for array query params ui/app/main.tsx	Adds stringifySearchValue and configures stringifySearch: stringifySearchWith(stringifySearchValue) alongside parseSearch: parseSearchWith(safeJsonParse) to serialize arrays as CSV and other values appropriately.
View logs dropdown items in customer, team, and virtual key tables ui/app/workspace/governance/views/customerTable.tsx, ui/app/workspace/governance/views/teamsTable.tsx, ui/app/workspace/virtual-keys/views/virtualKeysTable.tsx	Each table's actions menu gains a DropdownMenuItem rendering a routed Link to /workspace/logs with customer_ids, team_ids, or virtual_key_ids in the search params; imports updated to include Link and the ScrollText icon; clicks stop propagation and close the dropdown.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• maximhq/bifrost#3487: Related refactor that introduced the per-row action dropdowns used by the current "View logs" additions.
• maximhq/bifrost#3650: Related work on URL-driven multi-value log/dashboard filters and query-state parsing/serialization.
• maximhq/bifrost#3602: Related edits to the virtual-keys row actions dropdown behavior; touches the same component this PR extends.

Suggested reviewers

• akshaydeo
• danpiths

Poem

🐰 I hopped through routes with a little twitch,
Turning arrays to CSV without a hitch.
Customers, teams, keys—logs now in sight,
One click, one link, and the filters take flight.
CSV carrots crunch—navigation delight! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main feature: adding a 'View logs' menu item to three tables, which matches the actual changes across customerTable, teamsTable, and virtualKeysTable components.
Description check	✅ Passed	The description comprehensively covers the PR objectives, changes across all three components, design approach, testing steps, and security considerations, closely following the template structure.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 06-05-feat_allow_viewing_filtered_logs_for_governance_entities

---

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

[impoiler]

• fix: broaden Mantle model matching to all gpt variants #4091
• test: remove TestCollectApplicableGovernanceIDs_UserScopedModelConfigs #4090
• feat: add business unit CRUD, team assignment, and governance endpoints to OpenAPI spec #4082
• feat: add inline loading shell to #root before React mounts #4063
• fix: reduce FTS index left() cap from 800k to 250k chars to stay within tsvector limit #4057
• feat: add alias column to materialized view and filter support #4078
• feat: add "View logs" menu item to customer, team, and virtual key tables #4073 👈 (View in Graphite)
• feat: extract BudgetDisplay component with progress bar and tooltip #4055
• feat: add clickable links for routing rule, selected key, virtual key, and prompt in log detail views #4054
• fix: standardize page container layout with no-padding-parent and 100dvh sizing #4046
• fix: add colored tooltip values and subtle cursor highlight to dashboard charts #4044
• feat: add customer detail sheet and remove inline usage section from customer sheet #4026
• fix: replicates vk hierarchy flow for ghost nodes reconcilation #4088
• feat: supports multiple customers logs and usage tracking #4066
• fix: fixes virtual key model configs UI #4052
• fix: fixes cascade deletes for model configs #4051
• feat: adds support for multiple team and bu units in logstore #4041
• feat: adds team budget and rl collection exporters #4040
• dev

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

[greptile-apps]

Confidence Score: 5/5

Safe to merge; all three new View logs links pass array-typed IDs correctly and the global stringify change is consistent with how nuqs reads params elsewhere in the codebase.

The serialization logic is correct: arrays become comma-joined strings that nuqs parseAsArrayOf(parseAsString) can read, while numbers, booleans, and plain strings are unchanged from the router perspective. The same [id] array pattern already existed in logDetailView.tsx, so no new contract is introduced. No auth, data, or critical path is touched.

No files require special attention.

Important Files Changed

Filename	Overview
ui/app/main.tsx	Adds a custom stringifySearchValue function and wires it into the router stringifySearch; correctly handles primitive strings, numbers, booleans (raw), arrays (comma-joined), and objects (JSON).
ui/app/workspace/governance/views/customerTable.tsx	Adds View logs DropdownMenuItem using asChild + Link with customer_ids: [customer.id] array. Consistent with the approach used in logDetailView.tsx.
ui/app/workspace/governance/views/teamsTable.tsx	Adds View logs DropdownMenuItem with team_ids: [team.id] array. Correct param shape.
ui/app/workspace/virtual-keys/views/virtualKeysTable.tsx	Adds View logs DropdownMenuItem with virtual_key_ids: [vk.id] array. Correct param shape.

_{Reviews (4): Last reviewed commit: "feat: allow viewing filtered logs for Go..." | Re-trigger Greptile}

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ui/app/main.tsx`:
- Around line 26-31: The current stringifySearchValue uses JSON.stringify which
wraps primitive strings in quotes; change it so primitives are not quoted: in
stringifySearchValue, keep the Array.isArray branch, and for non-arrays return
String(value) for primitives (and handle null/undefined), but if value is a
non-null object keep JSON.stringify(value) so complex values remain
JSON-encoded; update the function stringifySearchValue accordingly to avoid
producing quoted string query params.

In `@ui/app/workspace/governance/views/customerTable.tsx`:
- Around line 82-95: The search prop passed to the Link in the DropdownMenuItem
uses search={{ customer_ids: customer.id }} but the logs route declares
customer_ids as an array; change this to pass an array (e.g., search={{
customer_ids: [customer.id] }}) so the contract matches. Update the Link where
to="/workspace/logs" and keep the existing onClick/onPointerDown handlers and
setIsOpen(false) behavior intact.

In `@ui/app/workspace/governance/views/teamsTable.tsx`:
- Around line 83-88: The Link currently passes team_ids as a single value;
change it to pass an array to match the downstream contract by wrapping the ID
in an array (e.g., pass search={{ team_ids: [team.id] }}). Update the Link
inside DropdownMenuItem (the element using team.name, team.id and calling
setIsOpen on click) so the logs page receives team_ids as an array of strings.

In `@ui/app/workspace/virtual-keys/views/virtualKeysTable.tsx`:
- Around line 220-229: The Link inside DropdownMenuItem currently passes
search={{ virtual_key_ids: vk.id }} but the logs route expects virtual_key_ids
to be an array; update the Link to pass the id wrapped in an array (e.g.,
virtual_key_ids: [vk.id]) so the contract (parseAsArrayOf(parseAsString)) is
satisfied—locate the Link within virtualKeysTable.tsx (the DropdownMenuItem /
Link block referencing vk.id) and change the search prop accordingly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5278b6f9-edb6-4cec-96a7-8df4bfffcf32

📥 Commits

Reviewing files that changed from the base of the PR and between 46aada1 and e9ef1b2.

📒 Files selected for processing (4)

• ui/app/main.tsx
• ui/app/workspace/governance/views/customerTable.tsx
• ui/app/workspace/governance/views/teamsTable.tsx
• ui/app/workspace/virtual-keys/views/virtualKeysTable.tsx

[CLAassistant]

All committers have signed the CLA.

[akshaydeo]

Merge activity

• Jun 5, 2:00 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 5, 2:17 PM UTC: Graphite rebased this pull request as part of a merge.
• Jun 5, 2:18 PM UTC: @akshaydeo merged this pull request with Graphite.