7:49 a.m.
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>
Is this too much hiding or maybe somebody has even more candidates for
suppressing?
Thanks,
Peter
7:53 a.m.
I personally am OK with this. Though most of these are related to Hawkular-Metrics and I
don't work much in that code base. So this is a question for the folks that develop
Metrics - they might need to see those categories at INFO level.
----- Original Message -----
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>
Is this too much hiding or maybe somebody has even more candidates for
suppressing?
Thanks,
Peter
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
8:02 a.m.
On 2015-06-04 14:53, John Mazzitelli wrote:
I personally am OK with this. Though most of these are related to
Hawkular-Metrics and I don't work much in that code base. So this is
a question for the folks that develop Metrics - they might need to
see those categories at INFO level.
Yes, they are free to set those back to INFO for their running instances
and the rest of the world does not need to suffer ;) -- P
----- Original Message -----
> 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>
>
> Is this too much hiding or maybe somebody has even more candidates for
> suppressing?
>
> Thanks,
>
> Peter
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
7:56 a.m.
+1 on the log tidy-up. There's too much information in the log right now and important
warnings/errors could be easily "lost" in the debug debris.
----- Original Message -----
From: "Peter Palaga" <ppalaga(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Thursday, June 4, 2015 2:49:41 PM
Subject: [Hawkular-dev] Which logging categories can be hidden by default?
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>
Is this too much hiding or maybe somebody has even more candidates for
suppressing?
Thanks,
Peter
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
7:57 a.m.
BTW, this little change belongs to the same topic:
https://github.com/hawkular/hawkular-metrics/pull/242 -- P
On 2015-06-04 14:49, Peter Palaga wrote:
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>
Is this too much hiding or maybe somebody has even more candidates for
suppressing?
Thanks,
Peter
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
11:20 a.m.
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3:25 p.m.
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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3:37 p.m.
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(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3:46 p.m.
New subject: Which logging categories can be hidden by default?
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(a)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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>
>>
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
1 p.m.
New subject: Which logging categories can be hidden by default?
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(a)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(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>>>
>>>
>>> _______________________________________________
>>> hawkular-dev mailing list
>>> hawkular-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>>
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3391
days inactive
3392
days old
10 comments
5 participants
participants (5)
-
John Mazzitelli -
John Sanda -
Peter Palaga -
Thomas Segismont -
Viliam Rockai