You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Log messages with domain metadata that is not [otp,sasl] or [otp] are being dropped by cth_log_redirect and will not show up in the ct log.
This resembles the default filter configuration of the default handler. However, the default configuration can be changed, while the domain filter in cth_log_redirect is hard coded.
To Reproduce
In a unit test with ?LOG(alert, "This is an alert", #{domain => [user, domain]}), the log message will not end up in the ct log at all and there is no way to change that through configuration.
Expected behavior
Message is part of the ct log (possibly after some kind of configuration has been applied).
Affected versions
OTP-26.2 (probably all versions that support logger).
The text was updated successfully, but these errors were encountered:
Yes, I agree that this behaviour is wrong. The hook should copy the filters from the default handler just as it does for formatter and level. That would allow the user to override the behaviour.
Not sure when we will have time to work on this, a PR will as always speed up the process.
Describe the bug
Log messages with
domain
metadata that is not[otp,sasl]
or[otp]
are being dropped by cth_log_redirect and will not show up in the ct log.This resembles the default filter configuration of the default handler. However, the default configuration can be changed, while the domain filter in cth_log_redirect is hard coded.
To Reproduce
In a unit test with
?LOG(alert, "This is an alert", #{domain => [user, domain]})
, the log message will not end up in the ct log at all and there is no way to change that through configuration.Expected behavior
Message is part of the ct log (possibly after some kind of configuration has been applied).
Affected versions
OTP-26.2 (probably all versions that support logger).
The text was updated successfully, but these errors were encountered: