[jira] [Updated] (CAMEL-6961) Make Camel core bundle configurable to generate less or smaller log messages itself

["Roman Minko (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Minko updated CAMEL-6961:
-------------------------------

    Description: 
Currently the Camel core generates easily lots of warning/error messages within the local log file. This makes it almost impossible to search for errors caused by other bundles, because the Camel bundle fills up about 99% of the log file content. Because the runtime will only store up to 11 log files log events are hard to find and also lost rather quickly (because older log files get deleted).
Looking through Camel code we can find something like this:
{code}
if (endpoint.getConsumer() == null) {
            LOG.warn("No consumers available on endpoint: " + endpoint + " to process: " + exchange);
            throw new DirectConsumerNotAvailableException("No consumers available on endpoint: " + endpoint, exchange);
        } else { 
{code}
The 	entire exchange put to the log before exception was thrown. It makes a huge log entries, which can not be turn off, unless we lost all the logs from Camel bundle. 
It will be very useful to have camel bundle logs configurable, to get more and less details by demand.  

  was:
Currently the Camel core generates easily lots of warning/error messages within the local log file. This makes it almost impossible to search for errors caused by other bundles, because the Camel bundle fills up about 99% of the log file content. Because the runtime will only store up to 11 log files log events are hard to find and also lost rather quickly (because older log files get deleted).
Looking through Camel code we can find something like this:
{code}
if (endpoint.getConsumer() == null) {
            LOG.warn("No consumers available on endpoint: " + endpoint + " to process: " + exchange);
            throw new DirectConsumerNotAvailableException("No consumers available on endpoint: " + endpoint, exchange);
        } else { 
{code}
The 	entire exchange put to the log before exception throw. It make a huge log entries, which can not be turn off, unless we lost all the logs from Camel bundle. 
It will be very useful to have camel bundle logs configurable, to get more and less details by demand.  


> Make Camel core bundle configurable to generate less or smaller log messages itself
> -----------------------------------------------------------------------------------
>
>                 Key: CAMEL-6961
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6961
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-blueprint, camel-core, osgi
>    Affects Versions: 2.12.1
>         Environment: Karaf osgi container, blueprint configuration
>            Reporter: Roman Minko
>            Priority: Minor
>
> Currently the Camel core generates easily lots of warning/error messages within the local log file. This makes it almost impossible to search for errors caused by other bundles, because the Camel bundle fills up about 99% of the log file content. Because the runtime will only store up to 11 log files log events are hard to find and also lost rather quickly (because older log files get deleted).
> Looking through Camel code we can find something like this:
> {code}
> if (endpoint.getConsumer() == null) {
>             LOG.warn("No consumers available on endpoint: " + endpoint + " to process: " + exchange);
>             throw new DirectConsumerNotAvailableException("No consumers available on endpoint: " + endpoint, exchange);
>         } else { 
> {code}
> The 	entire exchange put to the log before exception was thrown. It makes a huge log entries, which can not be turn off, unless we lost all the logs from Camel bundle. 
> It will be very useful to have camel bundle logs configurable, to get more and less details by demand.  



--
This message was sent by Atlassian JIRA
(v6.1#6144)