[Hawkular-dev] Which logging categories can be hidden by default?
Peter Palaga
ppalaga at redhat.com
Fri Jun 5 14:00:00 EDT 2015
I actually had the idea with sysprops which I also found quite good but
I was not brave enough to propose yet another way to pollute the pure
standalone.sh ;)
Here is the PR that I leave open for comments for a couple of days:
https://github.com/hawkular/hawkular/pull/192
-- P
On 2015-06-04 22:46, John Mazzitelli wrote:
> we could always use sysprops - that way no need for things like xmlstartlet just to tweek logging at startup. So for example:
>
> <logger category="org.apache.cassandra">
> <level name="${hawkular.logging.org.apache.cassandra:INFO}"/>
> </logger>
>
> So you can now just do this:
>
> standalone.sh -Dhawkular.logging.org.apache.cassandra=WARN
>
> or you can make it generic:
>
> <logger category="org.apache.cassandra">
> <level name="${hawkular.logging.level:INFO}"/>
> </logger>
> <logger category="org.whatever">
> <level name="${hawkular.logging.level:INFO}"/>
> </logger>
>
> so you can change blocks of categories with
>
> standalone.sh -Dhawkular.logging.level=WARN
>
> ----- Original Message -----
>> Thanks for the feedback. OK, let's have Cassandra and driver explicitly
>> there with INFO, so that folks not needing to see their INFO can easily
>> replace with WARN.
>>
>> So the present proposal is
>>
>> <logger category="org.apache.cassandra">
>> <level name="INFO"/>
>> </logger>
>> <logger category="org.jboss.as.ejb3">
>> <level name="WARN"/>
>> </logger>
>> <logger category="liquibase">
>> <level name="WARN"/>
>> </logger>
>> <logger category="org.ocpsoft.rewrite">
>> <level name="WARN"/>
>> </logger>
>> <logger category="com.datastax.driver">
>> <level name="INFO"/>
>> </logger>
>>
>>
>> FWIW, I started to use xmlstarlet command to adjust the logging levels
>> in standalone.xml just before starting a freshly built hawkular:
>>
>> yum install -y xmlstarlet
>> xmlstarlet ed --inplace --ps -N "l=urn:jboss:domain:logging:2.0" \
>> --update "//l:logger[@category='com.datastax.driver']/l:level/@name" \
>> --value INFO \
>> standalone/configuration/standalone-itest.xml
>>
>> -- P
>>
>>
>> On 2015-06-04 22:25, John Sanda wrote:
>>> With respect to Cassandra and the driver, I prefer to leave INFO level
>>> logging enabled for development. Collectively we do not have much
>>> experience with Cassandra. And considering we are using newer versions
>>> than were used in RHQ, we have even less experience. While the log
>>> messages might be a bit noisy, they can also be very helpful with the
>>> learning process.
>>>
>>>> On Jun 4, 2015, at 12:20 PM, Thomas Segismont <tsegismo at redhat.com> wrote:
>>>>
>>>> Le 04/06/2015 14:49, Peter Palaga a écrit :
>>>>> Hi *,
>>>>>
>>>>> I hope I am not the only one who finds that there is a lot of
>>>>> uninteresting messages in the log which can be made hidden by default.
>>>>>
>>>>> I propose to add the following lines to standalone xml files for both
>>>>> dev and production profiles:
>>>>>
>>>>> <logger category="org.apache.cassandra">
>>>>> <level name="WARN"/>
>>>>> </logger>
>>>>> <logger category="org.jboss.as.ejb3">
>>>>> <level name="WARN"/>
>>>>> </logger>
>>>>> <logger category="liquibase">
>>>>> <level name="WARN"/>
>>>>> </logger>
>>>>> <logger category="org.ocpsoft.rewrite">
>>>>> <level name="WARN"/>
>>>>> </logger>
>>>>> <logger category="com.datastax.driver">
>>>>> <level name="WARN"/>
>>>>> </logger>
>>>>
>>>> What are the lines you're trying to get rid of? In Metrics, I only see
>>>> these:
>>>>
>>>> 18:16:36,136 INFO
>>>> [com.datastax.driver.core.policies.DCAwareRoundRobinPolicy]
>>>> (metricsservice-lifecycle-thread) Using data-center name 'datacenter1'
>>>> for DCAwareRoundRobinPolicy (if this is incorrect, please provide the
>>>> correct datacenter name with DCAwareRoundRobinPolicy constructor)
>>>> 18:16:36,137 INFO [com.datastax.driver.core.Cluster]
>>>> (metricsservice-lifecycle-thread) New Cassandra host /127.0.0.1:9042 added
>>>>
>>>> Which I think are useful, just as:
>>>>
>>>> 18:16:19,517 INFO [org.wildfly.extension.undertow] (MSC service thread
>>>> 1-8) JBAS017519: Undertow HTTP listener default listening on
>>>> /127.0.0.1:8080
>>>>
>>>> Or:
>>>>
>>>> 18:16:20,574 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961:
>>>> Http management interface listening on http://127.0.0.1:9990/management
>>>>
>>>>>
>>>>> Is this too much hiding or maybe somebody has even more candidates for
>>>>> suppressing?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Peter
>>>>> _______________________________________________
>>>>> hawkular-dev mailing list
>>>>> hawkular-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>>>
>>>>
>>>> _______________________________________________
>>>> hawkular-dev mailing list
>>>> hawkular-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>
>>>
>>> _______________________________________________
>>> hawkular-dev mailing list
>>> hawkular-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>
>>
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
More information about the hawkular-dev
mailing list