-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Camel 4.5 - Trace config #5824
Comments
@davsclaus please take a look at the PR and I wonder if there is any way to test with these trace configuration? |
use null instead of empty string. For testing them I am afraid you can only test like its tested in the core project. But generally its not really needed as core tests the tracing functionality, and CEQ is just a facade on setting the options. |
zhfeng
added a commit
to zhfeng/camel-quarkus
that referenced
this issue
May 29, 2024
zhfeng
added a commit
to zhfeng/camel-quarkus
that referenced
this issue
May 30, 2024
zhfeng
added a commit
that referenced
this issue
May 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature here
The backlog tracer has its configuration moved into its own group like the debug already have
https://issues.apache.org/jira/browse/CAMEL-20472
Its probably easier to see what we did for CSB to learn what may need to be done in CEQ
apache/camel-spring-boot@3e8de47
There is a
DebugConfig.java
in CEQ today, so maybe aTraceConfig.java
needs to be created. As trace is very similar to how debug config is.The text was updated successfully, but these errors were encountered: