I've used ThresholdFilter to have the log level check at the level of the
(sub) appender:
"ThresholdFilter": {
"level": "${my:threadgroup.jobLogLevel}",
"onMatch": "ACCEPT",
"onMismatch": "DENY"
}
Of c
Another possibility would be to have a ThreadGroupContextSelector and then use
a different LoggerContext and configuration for each ThreadGroup. However, that
could get very complicated. The RoutingAppender pretty much accomplishes the
same thing and would be much easier to do.
Ralph
> On Apr
Oh damn, right, bit of a limitation there. I'll ponder on this a bit.
On Thu, 25 Apr 2019 at 11:18, Ralph Goers wrote:
>
> Matt, Benjamin’s issue is that he has no control over what is running in the
> “jobs” but he wants all the logs for a “job” to end up in the same appender.
> His definition
Matt, Benjamin’s issue is that he has no control over what is running in the
“jobs” but he wants all the logs for a “job” to end up in the same appender.
His definition of a job is that he is creating a thread to run it and
everything under that thread should route to that Appender. So he cannot
On Wed, 24 Apr 2019 at 18:47, Benjamin Jaton wrote:
> I've implemented the solution based on ThreadGroups. Now I am trying to
> have a separate log level per job. The goal is to be able to set one job in
> DEBUG or TRACE while the others stay in WARN. Possible?
> The RoutingAppender creates an app
