From: Michael Jeanson <mjeanson@efficios.com>
Date: Wed, 2 Feb 2022 19:04:50 +0000 (+0000)
Subject: fix: Convert custom loglevels in Log4j 2.x agent
X-Git-Url: http://git.liburcu.org/?a=commitdiff_plain;h=b6659287e99e16eb826ceff27b17cc1058967693;hp=b6659287e99e16eb826ceff27b17cc1058967693;p=lttng-ust.git

fix: Convert custom loglevels in Log4j 2.x agent

The loglevel integer representation has changed between log4j 1.x and
2.x, we currently convert the standard loglevels but passthrough the
custom ones.

This can be problematic when using severity ranges as custom loglevels
won't be properly filtered.

Use the same strategy as the upstream Log4j 2.x compatibility layer by
converting the custom loglevels to their equivalent standard loglevel
value.

Change-Id: I8cbd4706cb774e334380050cf0b407e19d7bc7c4
Signed-off-by: Michael Jeanson <mjeanson@efficios.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
---