The BacklogTracer in Camel core now has two new options added in 4.22:
activityEnabled — enables activity tracking, which captures a rolling window of completed exchange summaries with enriched span decorator attributes (Kafka topic, HTTP method, SQL query, etc.)activitySize — bounds the activity queue size (default 100, max 1000)
These were added in:
In camel-main, the dev profile auto-enables activity tracking via ProfileConfigurer.configureMain(). In camel-spring-boot, the CamelTraceAutoConfiguration handles the dev profile logic.
Please check if camel-quarkus needs code changes to:
- Expose
camel.trace.activity-enabled and camel.trace.activity-size as Quarkus configuration properties
- Auto-enable activity tracking when the dev profile is active
- Ensure the BacklogTracer wiring picks up these options at build time / runtime
It's possible that camel-quarkus already inherits this via camel-main's BaseMainSupport wiring — in that case this ticket can be closed as not-needed.
The BacklogTracer in Camel core now has two new options added in 4.22:
activityEnabled— enables activity tracking, which captures a rolling window of completed exchange summaries with enriched span decorator attributes (Kafka topic, HTTP method, SQL query, etc.)activitySize— bounds the activity queue size (default 100, max 1000)These were added in:
In camel-main, the dev profile auto-enables activity tracking via
ProfileConfigurer.configureMain(). In camel-spring-boot, theCamelTraceAutoConfigurationhandles the dev profile logic.Please check if camel-quarkus needs code changes to:
camel.trace.activity-enabledandcamel.trace.activity-sizeas Quarkus configuration propertiesIt's possible that camel-quarkus already inherits this via camel-main's
BaseMainSupportwiring — in that case this ticket can be closed as not-needed.