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
let log_file = self.log_directory.as_ref().map(|dir| prepare_log_file_name(dir));
LoggingConfig{
log_file,
log_to_stdout:self.foreground,
default_filter,
}
}
Instead, we should have INFO logging by default so that that you can see messages such as when the mount occurred successfully and where, even where users may capture logs without --debug specified.
This isn't as simple as changing one line of code. For this issue, we should review where we perform INFO logging in Mountpoint, and downgrade or adjust if necessary. For example, we should ensure that metric logging is turned off or downgraded when the customer does not specify --log-metrics.
The text was updated successfully, but these errors were encountered:
Today, Mountpoint uses
WARN
logging by default (and also disabled CRT logging entirely as it is noisy for our use case).mountpoint-s3/mountpoint-s3/src/cli.rs
Lines 498 to 526 in 76c3600
Instead, we should have
INFO
logging by default so that that you can see messages such as when the mount occurred successfully and where, even where users may capture logs without--debug
specified.This isn't as simple as changing one line of code. For this issue, we should review where we perform
INFO
logging in Mountpoint, and downgrade or adjust if necessary. For example, we should ensure that metric logging is turned off or downgraded when the customer does not specify --log-metrics.The text was updated successfully, but these errors were encountered: