Replies: 2 comments 6 replies
-
|
Hey, yes by setting this variable to false for example |
Beta Was this translation helpful? Give feedback.
-
|
Shouldn’t be possible, can you please post a complete code snippet that writes metadata on each line when false is set ? Have you set it to false for each Logger instance in your application? we have a regression test here one logger is adding the metadata per line and the other doesn’t |
Beta Was this translation helpful? Give feedback.
-
|
This reproduces for me in an isolated test |
Beta Was this translation helpful? Give feedback.
-
|
ah thanks for catching this, that configuration you are using in your example is to override the Logger formatter on the Sink level, currently that doesn't support changing the multi line message flag There are two formatters one on the Logger level and one on the Sink level, you have to do it on the Logger level Please pass int main()
{
std::shared_ptr<quill::Sink> console_sink;
quill::Backend::start();
quill::PatternFormatterOptions pattern_formatter_options;
pattern_formatter_options.format_pattern = "[%(time) %(logger)[%(process_id)][%(log_level)]] - %(message)";
pattern_formatter_options.timestamp_pattern = "%D %H:%M:%S.%Qms";
pattern_formatter_options.timestamp_timezone = quill::Timezone::LocalTime;
pattern_formatter_options.add_metadata_to_multi_line_logs = false;
quill::ConsoleSinkConfig config;
console_sink = quill::Frontend::create_or_get_sink<quill::ConsoleSink>("console_sink", std::move(config));
quill::Logger* logger = quill::Frontend::create_or_get_logger("test", console_sink, pattern_formatter_options);
logger->set_log_level(quill::LogLevel::Info);
LOG_INFO(logger, "{}", "my first line\nmy second line\nmy third line");
} |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the help! would never have gotten there on my own |
Beta Was this translation helpful? Give feedback.
-
|
This has been fixed on master for v10 so now your code snippet should also work correctly |
Beta Was this translation helpful? Give feedback.
-
|
For the stacktrace hex it’s because we sanitise non printable characters by default to hex you can disable this behaviour by setting for example an empty callback here quill/include/quill/backend/BackendOptions.h Line 217 in fb80e40 e.g https://quillcpp.readthedocs.io/en/latest/backend_options.html |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm nearly finished with upgrading to quill 9 (from 3) and I can't get my logs to look like they used to. When I have a multiline message, every line is getting a header. For instance, I'm trying to write a json message through the standard logger I log everything else to. This is for a log shipper that reads json from cout, but I'm getting
That used to be showing as
which makes my life much easier
Similarly, I use a library that prints source code on exceptions. This used to be nicely formatted with colors, but now I'm getting
The stacktraces in particular are very difficult to read. Is there any way to shut this behavior off?
Beta Was this translation helpful? Give feedback.
All reactions