This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-spring-boot.git

commit 5647b97c1e57b1b0d03ac36656d10874b7035244
Author: Claus Ibsen <[email protected]>
AuthorDate: Sun Feb 25 09:26:41 2024 +0100

    CAMEL-18858: camel-core - Mark route as created by Kamelet so we know this, 
so we can filter out in tooling and whereelse (kamelet is a blackbox)
---
 .../src/main/docs/spring-boot.json                 |  8 ++++++--
 .../spring/boot/CamelConfigurationProperties.java  | 23 ++++++++++++++++++++++
 2 files changed, 29 insertions(+), 2 deletions(-)

diff --git a/core/camel-spring-boot/src/main/docs/spring-boot.json 
b/core/camel-spring-boot/src/main/docs/spring-boot.json
index 6fbed54ac45..a456b72b6b8 100644
--- a/core/camel-spring-boot/src/main/docs/spring-boot.json
+++ b/core/camel-spring-boot/src/main/docs/spring-boot.json
@@ -987,12 +987,16 @@
     {
       "name": 
"camel.springboot.jmx-management-register-routes-create-by-kamelet",
       "type": "java.lang.Boolean",
-      "sourceType": "org.apache.camel.spring.boot.CamelConfigurationProperties"
+      "description": "Whether routes created by Kamelets should be registered 
for JMX management. Enabling this allows to have fine-grained monitoring and 
management of every route created via Kamelets. This is default disabled as a 
Kamelet is intended as a component (black-box) and its implementation details 
as Camel route makes the overall management and monitoring of Camel 
applications more verbose. During development of Kamelets then enabling this 
will make it possible for developers [...]
+      "sourceType": 
"org.apache.camel.spring.boot.CamelConfigurationProperties",
+      "defaultValue": false
     },
     {
       "name": 
"camel.springboot.jmx-management-register-routes-create-by-template",
       "type": "java.lang.Boolean",
-      "sourceType": "org.apache.camel.spring.boot.CamelConfigurationProperties"
+      "description": "Whether routes created by route templates (not Kamelets) 
should be registered for JMX management. Enabling this allows to have 
fine-grained monitoring and management of every route created via route 
templates. This is default enabled (unlike Kamelets) as routes created via 
templates is regarded as standard routes, and should be available for 
management and monitoring.",
+      "sourceType": 
"org.apache.camel.spring.boot.CamelConfigurationProperties",
+      "defaultValue": true
     },
     {
       "name": "camel.springboot.jmx-management-statistics-level",
diff --git 
a/core/camel-spring-boot/src/main/java/org/apache/camel/spring/boot/CamelConfigurationProperties.java
 
b/core/camel-spring-boot/src/main/java/org/apache/camel/spring/boot/CamelConfigurationProperties.java
index addd44dad82..11663104392 100644
--- 
a/core/camel-spring-boot/src/main/java/org/apache/camel/spring/boot/CamelConfigurationProperties.java
+++ 
b/core/camel-spring-boot/src/main/java/org/apache/camel/spring/boot/CamelConfigurationProperties.java
@@ -639,6 +639,29 @@ public class CamelConfigurationProperties extends 
DefaultConfigurationProperties
      */
     private boolean jmxUpdateRouteEnabled;
 
+    /**
+     * Whether routes created by Kamelets should be registered for JMX 
management. Enabling this allows to have
+     * fine-grained monitoring and management of every route created via 
Kamelets.
+     *
+     * This is default disabled as a Kamelet is intended as a component 
(black-box) and its implementation details as
+     * Camel route makes the overall management and monitoring of Camel 
applications more verbose.
+     *
+     * During development of Kamelets then enabling this will make it possible 
for developers to do fine-grained
+     * performance inspection and identify potential bottlenecks in the 
Kamelet routes.
+     *
+     * However, for production usage then keeping this disabled is recommended.
+     */
+    private boolean jmxManagementRegisterRoutesCreateByKamelet;
+
+    /**
+     * Whether routes created by route templates (not Kamelets) should be 
registered for JMX management. Enabling this
+     * allows to have fine-grained monitoring and management of every route 
created via route templates.
+     *
+     * This is default enabled (unlike Kamelets) as routes created via 
templates is regarded as standard routes, and
+     * should be available for management and monitoring.
+     */
+    private boolean jmxManagementRegisterRoutesCreateByTemplate = true;
+
     /**
      * If dumping is enabled then Camel will during startup dump all loaded 
routes (incl rests and route templates)
      * represented as XML/YAML DSL into the log. This is intended for trouble 
shooting or to assist during development.

Reply via email to