davsclaus opened a new pull request, #24600:
URL: https://github.com/apache/camel/pull/24600

   ## Summary
   
   _Claude Code on behalf of davsclaus_
   
   Adds a lightweight activity queue to the BacklogTracer that retains the last 
N completed exchange summaries, wires it into the CLI connector, and provides a 
`camel get activity` command to display the data.
   
   - **BacklogTracer activity queue** (`camel-api`, `camel-base-engine`): New 
bounded FIFO queue (default 100 entries) capturing metadata-only summaries 
(exchangeId, routeId, timestamp, elapsed, failed, endpointUri) when exchanges 
complete. Exposed via `getActivity()` / `dumpActivity()` on the `BacklogTracer` 
interface.
   - **ActivityDevConsole** (`camel-console`): New dev console (`activity`) 
exposing the activity queue as JSON. Uses `getActivity()` (non-destructive 
read) so repeated polling doesn't drain the queue.
   - **CLI connector** (`camel-cli-connector`): Writes `{pid}-activity.json` in 
`traceTask()` every 2nd cycle using overwrite mode.
   - **`camel get activity` command** (`camel-jbang-core`): Table display of 
recent exchange activity with `--sort`, `--limit`, `--filter` (route ID), 
`--short-uri`, `--wide-uri`, `--watch`, and `--json` options.
   - **Unit tests**: BacklogTracer activity queue tests (capture, overflow, 
clear-on-dump, failed exchanges) and ListActivity CLI command tests (empty 
output, entry display, route filter, JSON output, row limit).
   
   ## Test plan
   
   - [x] `BacklogTracerActivityTest` — 4 tests covering activity capture, 
overflow with bounded size, clear-on-dump, and failed exchange tracking
   - [x] `ListActivityTest` — 5 tests covering empty output, activity entry 
display, route filtering, JSON output mode, and row limiting
   - [ ] Manual: run a Camel integration, send messages, verify `camel get 
activity` displays the table correctly
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   Co-Authored-By: Claude Opus 4.6 <[email protected]>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to