lburgazzoli commented on issue #1564: URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-679831394
I don't think having an extension for camel-management would be a huge issue however I'd like to know more about the use case especially as it seems the main use case here seems to be relate to dev experience. In general I don't think traditional monitoring solution based on jmx are the right thing for camel-quarkus as the target is the cloud and containerized workload and exposing jmx is IMHO not the best. In my spare time I'm working with a colleague to see if we can have a standardized (under MicroProfile or SmallRye) way of exposing a similar experience but via plain REST endpoints (similar to the spring-boot actuators) so you can easily control who has access to what using the same technology you'd use to protect any REST endpoint. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
