Add application name (group) to ExecutionSummary search results #37

New Issue

claude · 2026-03-13T13:41:07+01:00

claude commented

2026-03-13 13:41:07 +01:00

Problem

ExecutionSummary only contains agentId (instance ID) but not group (application name). The UI needs the group to:

Show the correct application name in the results table (#70)
Navigate directly to the route diagram (/apps/:group/routes/:routeId) without a separate agent registry lookup (#69)
Group executions visually by application

Terminology

group = the application name (e.g. order-service-eu). All instances of the same Apache Camel application share a group. This is the HA/LB cluster.
agentId = a specific running instance of that application.

What's needed

Backend

Add group field to ExecutionSummary DTO
Populate from the execution's agent registry entry (or store directly in ClickHouse execution table)
Include in search result serialization

Frontend

Update openapi.json and regenerate schema.d.ts
ExecutionSummary type gains group: string
Remove the agent registry lookup workaround in ResultsTable.handleDiagramNav() which currently resolves agentId → group at navigation time

Blocked by this

#70 — Application column shows group instead of agentId
#69 — Direct row-click navigation needs group in the row data

## Problem `ExecutionSummary` only contains `agentId` (instance ID) but not `group` (application name). The UI needs the group to: - Show the correct application name in the results table (#70) - Navigate directly to the route diagram (`/apps/:group/routes/:routeId`) without a separate agent registry lookup (#69) - Group executions visually by application ### Terminology - **group** = the application name (e.g. `order-service-eu`). All instances of the same Apache Camel application share a group. This is the HA/LB cluster. - **agentId** = a specific running instance of that application. ## What's needed ### Backend - Add `group` field to `ExecutionSummary` DTO - Populate from the execution's agent registry entry (or store directly in ClickHouse execution table) - Include in search result serialization ### Frontend - Update `openapi.json` and regenerate `schema.d.ts` - `ExecutionSummary` type gains `group: string` - Remove the agent registry lookup workaround in `ResultsTable.handleDiagramNav()` which currently resolves `agentId → group` at navigation time ## Blocked by this - #70 — Application column shows group instead of agentId - #69 — Direct row-click navigation needs group in the row data

claude commented

2026-03-14 22:35:00 +01:00

Updated context post-UX overhaul (#69)

With direct row-click navigation, the results table becomes a launchpad — users scan and click. Having group visible in the table row is now more important than before, since the user needs to mentally connect the execution to its application context before clicking through.

Consider showing group as a subtle label above or beside the agent name in the Application column, so users can visually group executions by application before navigating.

**Updated context post-UX overhaul (#69)** With direct row-click navigation, the results table becomes a launchpad — users scan and click. Having `group` visible in the table row is now more important than before, since the user needs to mentally connect the execution to its application context before clicking through. Consider showing group as a subtle label above or beside the agent name in the Application column, so users can visually group executions by application before navigating.

claude referenced this issue

2026-03-15 10:12:37 +01:00

Fix Application column: show application name (group) instead of instance ID (agentId) #70

claude changed title from ~~Add agent name/group to ExecutionSummary search results~~ to Add application name (group) to ExecutionSummary search results

2026-03-15 10:12:50 +01:00

claude referenced this issue

2026-03-15 10:12:55 +01:00

UX overhaul: streamline navigation from search results to route diagram #69

claude referenced this issue

2026-03-17 10:12:42 +01:00

Fix Application column: show application name (group) instead of instance ID (agentId) #70

claude closed this issue

2026-04-01 22:23:55 +02:00

Sign in to join this conversation.