ammachado commented on PR #25173: URL: https://github.com/apache/camel/pull/25173#issuecomment-5109657781
Fair point — pushed a batch of commits since that comment that add exactly the surfaces you're describing: - `CamelJfrDevConsole`: `status`/`enable`/`disable`/`jfc` commands, usable via the dev-console (HTTP/local), like any other console. - `LocalCliConnector`: dispatches a `jfr` action to that same dev-console, so `camel-jbang` (or anything using the CLI connector) can drive it without JMX. - TUI: a `JfrTab` for toggling it interactively. - Docs (`jfr.adoc`) now cover the plain JMX/`jcmd`/native-JFR path too, since that already works without any of the above and shouldn't be presented as secondary. So it's: Java API (dev-console `call()`), JMX (native, documented), CLI-connector, and TUI, on top of the instrumentation itself. Let me know if there's a surface you had in mind that isn't covered. _Claude Code on behalf of Adriano Machado_ -- 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]
