You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this, I'm expecting that any classes under tld.domain will be logged at INFO level, but the application does not log any output for these classes unless I set log.level to a higher threshold.
Moreover, based on the format that I have, the class names and their packages must be logged, but with Camel only the class name is logged — and I guess that may be the actual issue.
This is the application output when I set log.level to INFO:
__ ____ __ _____ ___ __ ____ ______
--/ __ \/ / / / _ | / _ \/ //_/ / / / __/
-/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \
--\___\_\____/_/ |_/_/|_/_/|_|\____/___/
2024-12-26 23:26:48,519 |- INFO in org.apache.camel.quarkus.core.CamelBootstrapRecorder:46 [Quarkus Main Thread] - Apache Camel Quarkus 3.17.0 is starting
2024-12-26 23:26:48,520 |- INFO in org.apache.camel.main.MainSupport:71 [Quarkus Main Thread] - Apache Camel (Main) 4.9.0 is starting
2024-12-26 23:26:48,527 |- INFO in org.apache.camel.main.ProfileConfigurer:97 [Quarkus Main Thread] - The application is starting with profile: dev
2024-12-26 23:26:48,622 |- INFO in org.apache.camel.impl.engine.AbstractCamelContext:2524 [Quarkus Main Thread] - Apache Camel 4.9.0 (camel-1) is starting
2024-12-26 23:26:48,626 |- INFO in org.apache.camel.impl.engine.AbstractCamelContext:2727 [Quarkus Main Thread] - Routes startup (total:1)
2024-12-26 23:26:48,627 |- INFO in org.apache.camel.impl.engine.AbstractCamelContext:2731 [Quarkus Main Thread] - Started timer.route (timer://sampleTimer)
2024-12-26 23:26:48,627 |- INFO in org.apache.camel.impl.engine.AbstractCamelContext:2764 [Quarkus Main Thread] - Apache Camel 4.9.0 (camel-1) started in 4ms (build:0ms init:0ms start:4ms boot:380ms)
2024-12-26 23:26:48,703 |- INFO in io.quarkus:109 [Quarkus Main Thread] - application 0.0.0-SNAPSHOT on JVM (powered by Quarkus 3.17.4) started in 1.901s. Listening on: http://localhost:8080
2024-12-26 23:26:48,704 |- INFO in io.quarkus:113 [Quarkus Main Thread] - Profile dev activated. Live Coding activated.
2024-12-26 23:26:48,704 |- INFO in io.quarkus:115 [Quarkus Main Thread] - Installed features: [camel-core, camel-log, camel-timer, cdi, config-yaml, smallrye-context-propagation, vertx]
2024-12-26 23:26:49,633 |- INFO in ExampleRouteBuilder:14:166 [Camel (camel-1) thread #1 - timer://sampleTimer] - Checking the gravitational constant in your locale...
2024-12-26 23:26:52,626 |- INFO in ExampleRouteBuilder:14:166 [Camel (camel-1) thread #1 - timer://sampleTimer] - Checking the gravitational constant in your locale...
q
2024-12-26 23:26:53,681 |- INFO in org.apache.camel.impl.engine.AbstractCamelContext:2981 [Shutdown thread] - Apache Camel 4.9.0 (camel-1) is shutting down
2024-12-26 23:26:53,689 |- INFO in org.apache.camel.impl.engine.AbstractCamelContext:166 [Shutdown thread] - Routes stopped (total:1)
2024-12-26 23:26:53,689 |- INFO in org.apache.camel.impl.engine.AbstractCamelContext:166 [Shutdown thread] - Stopped timer.route (timer://sampleTimer)
2024-12-26 23:26:53,693 |- INFO in org.apache.camel.impl.engine.AbstractCamelContext:3112 [Shutdown thread] - Apache Camel 4.9.0 (camel-1) shutdown in 11ms (uptime:5s)
2024-12-26 23:26:53,701 |- INFO in io.quarkus:124 [Shutdown thread] - application stopped in 0.022s
And what I was mentioning is that these log statements should have the package names: tld.domain.route.ExampleRouteBuilder instead:
2024-12-26 23:26:49,633 |- INFO in ExampleRouteBuilder:14:166 [Camel (camel-1) thread #1 - timer://sampleTimer] - Checking the gravitational constant in your locale...
2024-12-26 23:26:52,626 |- INFO in ExampleRouteBuilder:14:166 [Camel (camel-1) thread #1 - timer://sampleTimer] - Checking the gravitational constant in your locale...
By the way, the same logging configuration I use it in almost all other Quarkus applications, that's why I think this may be something with Camel.
The text was updated successfully, but these errors were encountered:
Bug description
Description
I'm facing a small problem with the logging output. The current logging configuration is basically this:
With this, I'm expecting that any classes under
tld.domain
will be logged atINFO
level, but the application does not log any output for these classes unless I setlog.level
to a higher threshold.Moreover, based on the format that I have, the class names and their packages must be logged, but with Camel only the class name is logged — and I guess that may be the actual issue.
This is the application output when I set
log.level
toINFO
:And what I was mentioning is that these log statements should have the package names:
tld.domain.route.ExampleRouteBuilder
instead:By the way, the same logging configuration I use it in almost all other Quarkus applications, that's why I think this may be something with Camel.
The text was updated successfully, but these errors were encountered: