Creation of JsonAttributes before registering nlog web does not work about nlog.web

[snakefoot]

Yes NLog cannot recognize ${aspnet-request-url} until having registered/loaded the extensions from NLog.Web.AspNetCore.

You can also do this:

LogManager.Setup().RegisterNLogWeb();

var layout = new JsonLayout()
{
   Attributes =
   {
      new JsonAttribute("message", "${message}"),
      new JsonAttribute("url","${aspnet-request-url:IncludeQueryString=true}"),
   }
};

LogManager.Setup().LoadConfiguration(c => {
   c.ForLogger().WriteTo(new ColoredConsoleTarget { Layout = layout });
});

[ilya-scale]

Thanks, I actually just moved the code inside the LoadConfiguration lambda and it does work as well.

May I suggest that this string is just being remembered by the json attribute, and the first time it would indeed be used, it will do the resolution.

The way it works now is a bit unexpected.

[snakefoot]

When using unknown layoutrenderers (either because not registered or having misspelled the type-alias), then NLog will react early to tell where the issue is detected (and not late in the game).

But at the same time NLog really likes to swallow errors unless requested to throw exceptions. This mean that most issues leads to NLog complaining silently and not generating any output.

When troubleshooting "no output" then one either decide to activate ThrowConfigExceptions or enable the NLog InternalLogger.

[snakefoot]

Closing issue as answered due to inactivity.