log.debug("A tagged log message", userInfo: Dev.dave | Tag.sensitive)

That's somehow will confuse the user who only advantages one kind of Tag.
Then I suggest appending one demo code as below for that scenario.
log.debug("A tagged log message", userInfo: Tag.sensitive.dictionary)

const char* getIp(void) {
return "192.168.1.1";
}

above should be

const char* getIp(const el::LogMessage *l) {
return "192.168.1.1";
}

Currently reading the documentation for Key reveals it has an implementation Key: From<String>, however without dynamic-key feature enabled it is be super confusing when an error like `the trait bound

&'static str: std::convert::From<std::string::String>` is not satisfied

is encountered.

Hello. I am trying to migrate my project from basic logging to something more advanced and someone recommended this module through reddit. I have been through the quick-start guide and other available documentation and have some very basic questions about the API.

How can I parse the logs and format them for the stdout?

Is there a way to stream what's being written to the log, just like the

Bug Report

Version

-> % cargo tree | grep tracing
├── tracing v0.1.13
│   ├── tracing-attributes v0.1.7
│   └── tracing-core v0.1.10
├── tracing-futures v0.2.4
│   └── tracing v0.1.13 (*)
├── tracing-log v0.1.1
│   └── tracing-core v0.1.10 (*)
├── tracing-subscriber

Typing console.log("%s has %d points", "Sam", 100);
outputs - %s has %d points Sam 100, (concatenation) on the page,
while the console outputs - Sam has 100 points
(It substitutes the values of %s & %d in the string).

Reference link

When you use the formatter: ::Logger::Formatter the output does not prepend the config.log_tags.

What's interesting is the LogStashLogger::Formatter::* all include "tags":["127.0.0.1"] in the output.

Should be fairly straightforward, we can do the same thing we did for the syslog3/4 distinction for adding support for syslog 5. Main work is in rewriting full examples to use syslog 5.

There were some things that syslog 3 could do, but syslog 4 couldn't. I can't remember off the top of my head what they were. If syslog 5 fixes these, and is at least as capable as both syslog 3 and 4, we can re

Can you be useful for debugging a production app, since you wouldn't otherwise easily see the logging from the main process.

@acheronfail Thoughts?

Bug

NLog version: 4.6.8
NLog.Extensions.Logging version: 1.6.1
NLog.Web.AspNetCore version: 4.9.0

Platform: .NET Core 3.2
Current NLog config

<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      autoReload="true"
      internalLogLevel="In

We should ensure in all scenarios we don't run out of memory. I'm not sure the current usage but the queues should be cleared every 10 seconds.

It could be great to have a placeholder that represents the current uptime of application, e.g. {uptime}. The init time may be the same as the logger initialization time.

Even if you don't like this proposal, it might be solved by the posiblity of being able to register custom placeholder.

In my app I create a logger using:

def create_logger(log_path, log_name, log_level=logging.INFO):
    daiquiri.setup(
        level=log_level,
        outputs=(daiquiri.output.File(
            directory=log_path, program_name=log_name), 
            daiquiri.output.STDOUT,))

    return daiquiri.getLogger(program_name=log_name)

When I look at the console, I see logs for

Timber's various configuration parameters do not consistently support pulling values via a {:system, "VAR_NAME"} tuple. For example, Timber.Config.api_key/0 does, yet [Timber.Config.http_url/0](https://github.com/timberio/timber-elixir/blob/20ec4a520fe94f15b5812337cfc8a54528aff