-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #15126: Add verbosity level in the rudder logger #1006
Fixes #15126: Add verbosity level in the rudder logger #1006
Conversation
tree/20_cfe_basics/log_rudder.cf
Outdated
# @name Log for Rudder with mode | ||
# @description Logging different verbosity outputs for Rudder reports | ||
# | ||
# @parameter mode The mode use to make the report (can be info, normal, debug) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
normal is a weird verbosity level
methods: | ||
# Report using the appropriate bundle(s) | ||
"wrapper for ${configuration.enabled_loggers}" | ||
usebundle => log_rudder_mode("${mode}", "${message}", "${class_parameter}", "${old_class_prefix}", "${class_prefix}", "@{args}"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in 5.1, ncf cannot be standalone anymore.
do we really need this method ? can't we simply use the log_rudder_mode ?
or do you expect that we need some layer of indirection for the future ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are definitely right, we do not need another layer of indirection, this will only make things less understandable.
…configurable_ncf_pr'
eea442e
to
b9c0f39
Compare
retarget to 5.1, too much diff to do, I will recreate a pull request starting in 5.1 |
new PR here: #1048 |
https://issues.rudder.io/issues/15126