[ 
https://issues.apache.org/jira/browse/CAMEL-26941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-26941:
-----------------------------------

    Assignee: Claus Ibsen

> camel-jbang - camel status <name> --json: the state of an integration in one 
> call
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-26941
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26941
>             Project: Camel
>          Issue Type: Sub-task
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.24.0
>
>
> Measured on 2026-11-13 with the unpacked 4.24.0-SNAPSHOT camel-launcher on 
> macOS (Apple M4 Pro, JDK 25), warm CDS archives, medians of 5-9 runs on a 
> machine with other load (treat as +/-30 %). Estimates are marked as such. 
> Paths are relative to {{dsl/camel-jbang/}}.
> After {{camel run}} or an edit, an agent checks an integration with 3-4 
> commands (get route, get health, get error, log), each a new JVM of 0.25-0.5 
> s: about 1 s per check today. The data is already in {{<pid>-status.json}} 
> (about 30 KB) and the error file.
> Proposal: {{camel status <name> --json}} that returns in one document the 
> state and phase, the routes with their state and counters, health, the last 
> errors, the last reload outcome, the ports and endpoints, and the tail of the 
> log (with a limit). The MCP server could offer the same as one tool. The same 
> JSON shape rules apply as in CAMEL-25388 (one document, pid as a number, 
> {{uptime}} with one meaning).
> _Claude Code on behalf of Claus Ibsen_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to