Log appenders not reliably differentiating between warn and error log events

[mountaindude]

What version of Butler SOS are you using?

7.0.7

What version of Node.js are you using? Not applicable if you use the standalone version of Butler SOS.

16.4.0

What command did you use to start Butler SOS?

node butler-sos.js

What operating system are you using?

macOS Monterey

What CPU architecture are you using?

x86_64

What Qlik Sense versions are you using?

2021-November

Describe the Bug

It seems that Qlik Sense does not reliably report warnings and errors via custom log appenders.

Currently Butler SOS uses this row in the XML log appenders:

<param name="threshold" value="warn" />

The idea is then that the log appender should report all warnings and errors and fatal messages to Butler SOS.
But... it seems that this is not the case.
Some messages that show up in log files (for example errors in the scheduler's log files when reload tasks fail) never make it to Butler SOS.

There is an alternate syntax that could be tried.
According to Log4Net documentation it's just an alias for the currently used syntax, but a few tests indicate that the expected log events do make it to Butler SOS:

<threshold value="warn" />

Unclear what's going on here. Have tried restarting all affected services too, but the inconsistent event delivery remained.

Let's try the new syntax and see if it works better.

Expected Behavior

No response

To Reproduce

No response