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

New Issue

claude · 2026-03-15T10:12:37+01:00

claude commented

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

Problem

The "Application" column in the results table currently displays agentId, which is the ID of an individual running instance (pod/container). Users care about which application an execution belongs to, not which specific instance handled it.

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 (one pod/VM/container).

Current behavior

"Application" column shows agentId (instance-level, e.g. order-service-eu-7f4d8b-xk2p9)
AppBadge component renders the agentId
ExecutionSummary schema has agentId but no group field (see #37)

Expected behavior

"Application" column shows the group (application name, e.g. order-service-eu)
The specific agentId (instance) can be shown as secondary info on hover or in the detail view
This requires #37 to land first (adding group to ExecutionSummary)

Scope

Update ResultsTable.tsx — Application column renders group instead of agentId
Update AppBadge.tsx — accept group as primary label, agentId as secondary/tooltip
Update ExchangeDetail.tsx — show both Application (group) and Instance (agentId) in metadata
Update RoutePage breadcrumb/header — already uses group correctly

Depends on

#37 — Add agent name/group to ExecutionSummary (backend change to include group in search results)

## Problem The "Application" column in the results table currently displays `agentId`, which is the ID of an individual running instance (pod/container). Users care about *which application* an execution belongs to, not which specific instance handled it. ### 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 (one pod/VM/container). ### Current behavior - "Application" column shows `agentId` (instance-level, e.g. `order-service-eu-7f4d8b-xk2p9`) - `AppBadge` component renders the agentId - `ExecutionSummary` schema has `agentId` but no `group` field (see #37) ### Expected behavior - "Application" column shows the **group** (application name, e.g. `order-service-eu`) - The specific `agentId` (instance) can be shown as secondary info on hover or in the detail view - This requires #37 to land first (adding `group` to `ExecutionSummary`) ## Scope - Update `ResultsTable.tsx` — Application column renders group instead of agentId - Update `AppBadge.tsx` — accept group as primary label, agentId as secondary/tooltip - Update `ExchangeDetail.tsx` — show both Application (group) and Instance (agentId) in metadata - Update `RoutePage` breadcrumb/header — already uses group correctly ## Depends on - #37 — Add agent name/group to ExecutionSummary (backend change to include `group` in search results)

claude referenced this issue

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

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

claude referenced this issue

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

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

claude commented

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

Duplicate of #37 — same root cause: groupName is missing from the ExecutionSummary DTO. Fixing #37 resolves both. Closing as duplicate.

Duplicate of #37 — same root cause: `groupName` is missing from the `ExecutionSummary` DTO. Fixing #37 resolves both. Closing as duplicate.

claude closed this issue

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