and sets the level to OFF we still want INFO and below to be
logged.
Thanks,
Nick
Subject: Re: redefining existing levels?
From: remko.po...@gmail.com
Date: Wed, 26 Aug 2015 09:25:09 +0900
To: log4j-user@logging.apache.org
Could you explain a bit more about your use case before we zoom
the
log4net configuration in the application configuration file. So it for
instance it's a web application, touching the log4net configuration will
restart the application domain.
Thanks,
Nick
Date: Wed, 26 Aug 2015 09:32:15 -0700
Subject: Re: redefining existing levels?
From: garydgreg
we'll call always on or 24x7 logging. This is
about always having INFO and more critical turned on. I'm just looking for
ways to help enforce that.
Thanks,
Nick
Date: Wed, 26 Aug 2015 09:24:07 -0700
Subject: Re: redefining existing levels?
From: garydgreg...@gmail.com
To: log4j-user
logging. This is
about always having INFO and more critical turned on. I'm just looking for
ways to help enforce that.
Thanks,
Nick
Date: Wed, 26 Aug 2015 09:24:07 -0700
Subject: Re: redefining existing levels?
From: garydgreg...@gmail.com
To: log4j-user@logging.apache.org
On Wed
critical levels to be on no matter what.
But if a user gets in a config file and sets the root level to off, how can
you stop him or her from removing your filters and custom levels?
Gary
Thanks,
Nick
Subject: Re: redefining existing levels?
To: log4j-user@logging.apache.org
From: x...@dds.nl
I should have add:
ways to enforce that via configuration. We don't want to do it via code and
we don't want to have to rely on some of our code being run at startup.
Thanks,
Nick
From: nic...@msn.com
To: log4j-user@logging.apache.org
Subject: RE: redefining existing levels?
Date: Wed, 26
-0700
Subject: Re: redefining existing levels?
From: garydgreg...@gmail.com
To: log4j-user@logging.apache.org
On Wed, Aug 26, 2015 at 9:19 AM, Nicholas Duane nic...@msn.com wrote:
I guess the main use case we're trying to solve is someone, maybe some
admin or maybe a developer asking
of INFO and below (or above for .NET) events. So even if
something thinks they should turn off logging and sets the level to OFF we
still want INFO and below to be logged.
Thanks,
Nick
Subject: Re: redefining existing levels?
From: remko.po...@gmail.com
Date: Wed, 26 Aug 2015 09:25:09 +0900
and sets the root level to off, how can
you stop him or her from removing your filters and custom levels?
Gary
Thanks,
Nick
Subject: Re: redefining existing levels?
To: log4j-user@logging.apache.org
From: x...@dds.nl
Date: Wed, 26 Aug 2015 17:55:23 +0200
I think it is still unclear
to turn of logging of INFO and below levels.
Thanks,Nick
Original message
From: Nicholas Duane nic...@msn.com
Date: 08/25/2015 7:46 PM (GMT-07:00)
To: Log4J Users List log4j-user@logging.apache.org
Subject: RE: redefining existing levels?
Yes and no. The user might know how
to be logged.
Thanks,
Nick
Subject: Re: redefining existing levels?
From: remko.po...@gmail.com
Date: Wed, 26 Aug 2015 09:25:09 +0900
To: log4j-user@logging.apache.org
Could you explain a bit more about your use case before we zoom in on a
specific solution?
I'd like
things off.
Basically, we have what we'll call always on or 24x7 logging. This is
about always having INFO and more critical turned on. I'm just looking for
ways to help enforce that.
Thanks,
Nick
Date: Wed, 26 Aug 2015 09:24:07 -0700
Subject: Re: redefining existing levels?
From: garydgreg
.
Thanks,
Nick
Date: Wed, 26 Aug 2015 09:32:15 -0700
Subject: Re: redefining existing levels?
From: garydgreg...@gmail.com
To: log4j-user@logging.apache.org
On Wed, Aug 26, 2015 at 9:27 AM, Nicholas Duane nic...@msn.com wrote:
Maybe what I'm trying to do is not that useful. However, I'm
be doing, like
turning logging to OFF, we would like INFO and more critical levels to still
be flowing.
Thanks,
Nick
Subject: Re: redefining existing levels?
To: log4j-user@logging.apache.org
From: x...@dds.nl
Date: Wed, 26 Aug 2015 17:56:10 +0200
Op 26-8-2015 om 5:43 schreef Gary
the same thing
could be done with log4j.
Thanks,
Nick
Subject: Re: redefining existing levels?
From: ralph.go...@dslextreme.com
Date: Wed, 26 Aug 2015 09:31:19 -0700
To: log4j-user@logging.apache.org
Can’t you just put a comment in the config file that states the minimum
logging level
that.
Thanks,
Nick
Date: Wed, 26 Aug 2015 09:24:07 -0700
Subject: Re: redefining existing levels?
From: garydgreg...@gmail.com
To: log4j-user@logging.apache.org
On Wed, Aug 26, 2015 at 9:19 AM, Nicholas Duane nic...@msn.com
wrote:
I guess
configuration
only, not being able to turn of logging of INFO and below levels.
Thanks,Nick
Original message
From: Nicholas Duane nic...@msn.com
Date: 08/25/2015 7:46 PM (GMT-07:00)
To: Log4J Users List log4j-user@logging.apache.org
Subject: RE: redefining existing levels
and below levels.
Thanks,Nick
Original message
From: Nicholas Duane nic...@msn.com
Date: 08/25/2015 7:46 PM (GMT-07:00)
To: Log4J Users List log4j-user@logging.apache.org
Subject: RE: redefining existing levels?
Yes and no. The user might know how to turn on/off logging
:46 PM (GMT-07:00)
To: Log4J Users List log4j-user@logging.apache.org
Subject: RE: redefining existing levels?
Yes and no. The user might know how to turn on/off logging, but they might
not understand what the enterprise is wanting to do. We would like to make
it hard, if not impossible
Thanks. I assumed my 'BUSINESS' level is working using the CustomLevel,
though I haven't tried it yet as I was trying to validate redefining existing
level.
Thanks,
Nick
Date: Tue, 25 Aug 2015 14:32:01 -0700
Subject: Re: redefining existing levels?
From: garydgreg...@gmail.com
To: log4j
Nicholas,
Yes, please see
https://logging.apache.org/log4j/2.x/manual/customloglevels.html
If the documentation can be improved, please let us know how.
Gary
On Tue, Aug 25, 2015 at 12:42 PM, Nicholas Duane nic...@msn.com wrote:
Can existing log4j2 levels be redefined? I'm able to do this
existing level.
Thanks,
Nick
Date: Tue, 25 Aug 2015 14:32:01 -0700
Subject: Re: redefining existing levels?
From: garydgreg...@gmail.com
To: log4j-user@logging.apache.org
Nick,
Your BUSINESS level should be configurable per
https://logging.apache.org/log4j/2.x/manual
filter as we also
need that to work. It works in .NET. So far it's looking like I'll need to
write my own filter for log4j2 in order to get range level filtering working.
Thanks,
Nick
Date: Tue, 25 Aug 2015 15:54:08 -0700
Subject: Re: redefining existing levels?
From: garydgreg
filter for log4j2 in order to get
range level filtering working.
Thanks,
Nick
Date: Tue, 25 Aug 2015 15:54:08 -0700
Subject: Re: redefining existing levels?
From: garydgreg...@gmail.com
To: log4j-user@logging.apache.org
Ah, well, let's start with the documented stuff we know should
filtering working.
Thanks,
Nick
Date: Tue, 25 Aug 2015 15:54:08 -0700
Subject: Re: redefining existing levels?
From: garydgreg...@gmail.com
To: log4j-user@logging.apache.org
Ah, well, let's start with the documented stuff we know should work ;-)
Gary
On Tue, Aug 25
needed.
Thanks,
Nick
Date: Wed, 26 Aug 2015 08:33:34 +0900
Subject: Re: redefining existing levels?
From: remko.po...@gmail.com
To: log4j-user@logging.apache.org
Is redefining levels a way to work around the issue you had with the range
check?
I've replied to your range check question
+0900
Subject: Re: redefining existing levels?
From: remko.po...@gmail.com
To: log4j-user@logging.apache.org
Is redefining levels a way to work around the issue you had with the
range
check?
I've replied to your range check question with a link to an example
config.
On Wed, Aug
I guess I should have mentioned, though it's probably obvious, that I'm only
interested in a configuration based solution. I'm not looking for a code
solution.
Thanks,
Nick
From: nic...@msn.com
To: log4j-user@logging.apache.org
Subject: RE: redefining existing levels?
Date: Tue, 25 Aug 2015
, though it's probably obvious, that I'm
only interested in a configuration based solution. I'm not looking for a
code solution.
Thanks,
Nick
From: nic...@msn.com
To: log4j-user@logging.apache.org
Subject: RE: redefining existing levels?
Date: Tue, 25 Aug 2015 16:05:47 -0400
Thanks
29 matches
Mail list logo
