What you describes matches in my mind a Loggers. Your whole app can have a
"Business" logger and sub-categories if you need them like
"Business.Accounting", and "Business.HR".
Gary
On Tue, Sep 8, 2015 at 6:09 PM, Nicholas Duane wrote:
>
>
>
> I looked over that stackoverflow
Can you please clarify, “If we had some way to know an event is a business
event we wouldn’t need level”? I do not understand how you can code
logger.log(BUSINESS, msg) but you cannot code logger.info(BUSINESS, msg).
Ralph
> On Sep 8, 2015, at 6:09 PM, Nicholas Duane wrote:
I looked over that stackoverflow post and I'm still not seeing a good match as
a way for us to log our business events.
A business event I guess is an event which extends whatever schema we come up
with for a business event. While an instance of this schema could be logged at
any level,
Or
Logger logger = LogManager.getLogger("Business");
...
logger.info("Hello");
Gary
On Tue, Sep 8, 2015 at 7:24 PM, Ralph Goers
wrote:
> Can you please clarify, “If we had some way to know an event is a business
> event we wouldn’t need level”? I do not understand
Let's say we have a schema where one of the properties is "category".
"category" could be "info", "warn", "business", "audit", etc. I could use that
property to forward the events to the appropriate places. We don't have that
property because I guess we don't think we need it. The current
I was just about to reply to your previous email about using a single
"business" logger, or some hierarchy of business loggers, to log business
events and say that we might go that route. However, now that you brought up
the post from Ralph, which I just replied to, I'm thinking a logger won't
The bottom line is it doesn’t matter which log level they use. With the
configuration below ALL business events will be accepted, meaning the log level
on the logger will not be checked. Then every logger would have a marker
filter to accept or deny the event