You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/02/04 14:32:00 UTC

[GitHub] [camel-k] nicolaferraro opened a new issue #2000: Logging configuration does not affect integrations

nicolaferraro opened a new issue #2000:
URL: https://github.com/apache/camel-k/issues/2000


   Setting `logging.level.org.apache.camel=DEBUG` does not affect integration logs.
   
   So if users set flag `--logging-level org.apache.camel=DEBUG`, that is currently translated into the property above and does not work.
   
   The correct mapping should be something like: `quarkus.log.category."org.apache.camel".level=DEBUG`
   
   We should also change the doc to point to the Quarkus documentation for configuring the log via properties.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [camel-k] astefanutti commented on issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #2000:
URL: https://github.com/apache/camel-k/issues/2000#issuecomment-855809142


   > +1 for that. I can send a PR this week with the proposed code to remove it.
   
   Great, thanks!
   


-- 
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:
users@infra.apache.org

[GitHub] [camel-k] lburgazzoli commented on issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #2000:
URL: https://github.com/apache/camel-k/issues/2000#issuecomment-773358482


   with the main runtime there were some code to translate the property to the log4j2 format, maybe we should do the same here ? or map directly to the quarkus ones ?


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [camel-k] orpiske commented on issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
orpiske commented on issue #2000:
URL: https://github.com/apache/camel-k/issues/2000#issuecomment-831142294


   I am going to take care of this issue as part of the logging trait changes. 


-- 
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:
users@infra.apache.org

[GitHub] [camel-k] lburgazzoli commented on issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #2000:
URL: https://github.com/apache/camel-k/issues/2000#issuecomment-773358482


   with the main runtime there were some code to translate the property to the log4j2 format, maybe we should do the same here ? or map directly to the quarkus ones ?


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [camel-k] nicolaferraro commented on issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #2000:
URL: https://github.com/apache/camel-k/issues/2000#issuecomment-773367316


   > with the main runtime there were some code to translate the property to the log4j2 format, maybe we should do the same here ? or map directly to the quarkus ones ?
   
   Allowing the `logging.level.` syntax and map them to quarkus would be better I think


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [camel-k] nicolaferraro commented on issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #2000:
URL: https://github.com/apache/camel-k/issues/2000#issuecomment-773367316


   > with the main runtime there were some code to translate the property to the log4j2 format, maybe we should do the same here ? or map directly to the quarkus ones ?
   
   Allowing the `logging.level.` syntax and map them to quarkus would be better I think


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [camel-k] astefanutti commented on issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #2000:
URL: https://github.com/apache/camel-k/issues/2000#issuecomment-855786724


   @orpiske with your work on the _logging_ trait, I think we could "simply" remove the `--logging-level` option from the `run` command, and have it replaced with `-t logging.level`. WDYT?


-- 
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:
users@infra.apache.org

[GitHub] [camel-k] astefanutti closed issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
astefanutti closed issue #2000:
URL: https://github.com/apache/camel-k/issues/2000


   


-- 
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:
users@infra.apache.org

[GitHub] [camel-k] astefanutti commented on issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #2000:
URL: https://github.com/apache/camel-k/issues/2000#issuecomment-857903010


   Fixed with #2377.


-- 
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:
users@infra.apache.org

[GitHub] [camel-k] orpiske commented on issue #2000: Logging configuration does not affect integrations

Posted by GitBox <gi...@apache.org>.
orpiske commented on issue #2000:
URL: https://github.com/apache/camel-k/issues/2000#issuecomment-855807777


   > @orpiske with your work on the _logging_ trait, I think we could "simply" remove the `--logging-level` option from the `run` command, and have it replaced with `-t logging.level`. WDYT?
   
   +1 for that. I can send a PR this week with the proposed code to remove it. 


-- 
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:
users@infra.apache.org