entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-2|blocks|key|a51p6|text|我们使用Serilog+(应该与NLog大致相同)。它与来自Aspnet核心的ILogger有很好的集成。|unstyled|depth|inlineStyleRanges|entityRanges|aujqh|您可以创建中间件并使用ILogger.BeginScope|offset|length|style|CODE|3sceq|public+class+LoggerMiddleware
{
++++private+readonly+RequestDelegate+_next;
++++private+readonly+ILogger<LoggerMiddleware>+_logger;

++++public+LoggerMiddleware(RequestDelegate+next,+ILogger<LoggerMiddleware>+logger)
++++{
++++++++_next+=+next;
++++++++_logger+=+logger;
++++}

++++public+async+Task+Invoke(HttpContext+context)
++++{
++++++++var+dictionary+=+new+Dictionary<string,+object>
++++++++{
++++++++++++{+"Username",+context.User?.Identity?.Name;+}
++++++++};

++++++++using+(_logger.BeginScope(dictionary))
++++++++{
++++++++++++await+_next(context);
++++++++}
++++}
}|code-block|syntax|javascript|3o9o7|通过我们的Serilog集成，我们能够在我们的日志模板中使用Username，并且它在整个HTTP调用过程中被保留(使用不同的线程)。|bg5ut|按照这个维基https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-2，你的NLog积分应该是类似的|fu3t0^0|0|B|I|0|0|U|8|0|6|21|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|Y|G|@]|H|@]|6|$]]|$A|I|C|J|2|E|F|Z|G|@$K|10|L|11|M|N]]|H|@]|6|$]]|$A|O|C|P|2|Q|F|12|G|@]|H|@]|6|$R|S]]|$A|T|C|U|2|E|F|13|G|@$K|14|L|15|M|N]]|H|@]|6|$]]|$A|V|C|W|2|E|F|16|G|@]|H|@$K|17|L|18|A|19]]|6|$]]|$A|X|C|-4|2|E|F|1A|G|@]|H|@]|6|$]]]]

We use Serilog (should be more or less equivalent with NLog). It has a very good integration with the ILogger from Aspnet core.

You can create a middleware and use the <code>ILogger.BeginScope</code>

<pre><code>public class LoggerMiddleware
{
 private readonly RequestDelegate _next;
 private readonly ILogger&lt;LoggerMiddleware&gt; _logger;

 public LoggerMiddleware(RequestDelegate next, ILogger&lt;LoggerMiddleware&gt; logger)
 {
 _next = next;
 _logger = logger;
 }

 public async Task Invoke(HttpContext context)
 {
 var dictionary = new Dictionary&lt;string, object&gt;
 {
 { "Username", context.User?.Identity?.Name; }
 };

 using (_logger.BeginScope(dictionary))
 {
 await _next(context);
 }
 }
}
</code></pre>

With our Serilog integration, we are able to use <code>Username</code> in our log templates and it's preserved throughout the HTTP call (with different threads).

You NLog integeration should be similar following this wiki <a href="https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-2" rel="nofollow noreferrer">https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-2</a>

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://www.nuget.org/packages/NLog.Web.AspNetCore/|1|https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.httpcontext.traceidentifier|2|https://nlog-project.org/config/?tab=layout-renderers&search=package:nlog.web.aspnetcore|3|https://docs.microsoft.com/en-us/dotnet/api/system.threading.asynclocal-1|4|https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.ilogger.beginscope|5|https://github.com/NLog/NLog.Extensions.Logging/wiki/NLog-properties-with-Microsoft-Extension-Logging#beginscope|6|https://github.com/NLog/NLog/wiki/MDLC-Layout-Renderer#scoped-item|blocks|key|46q31|text|NLog.Web.AspNetCore提供了大量的布局渲染器，可以捕获用于日志记录的HttpRequest-context-properties+(不需要注入NLog+MDLC)。|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|fkq59|这将探测HttpRequest-Header中的值JSNLog-RequestId，如果为空，则回退到AspNetCore-RequestId值，如果也为空，则回退到AspNetCore-TraceIdentifer|style|CODE|cd4j0|${aspnet-request:header=JSNLog-RequestId:whenEmpty=${mdlc:item=RequestId:whenEmpty=${aspnet-traceIdentifier}}}|code-block|syntax|javascript|cr6an|可用${aspnet}+Layout-renderers列表|blj6f|NLog在NetCore上使用AsyncLocal，如果使用的是微软扩展日志记录(MEL)，则可以使用ILogger.BeginScope将属性注入NLog+MDLC+(并在离开作用域时清除)|99brn|也可以使用MappedDiagnosticsLogicalContext.SetScoped填充using+MDLC，当离开NLog+-scope时也会将其清除。|caonv^0|0|J|0|0|P|G|2B|P|1|0|0|2|Q|2|0|F|A|3|1F|I|4|22|9|5|0|5|15|6|0^^$0|$1|$2|3|4|5|6|$7|8]]|9|$2|3|4|5|6|$7|A]]|B|$2|3|4|5|6|$7|C]]|D|$2|3|4|5|6|$7|E]]|F|$2|3|4|5|6|$7|G]]|H|$2|3|4|5|6|$7|I]]|J|$2|3|4|5|6|$7|K]]]|L|@$M|N|O|P|2|Q|R|1C|S|@]|T|@$U|1D|V|1E|M|1F]]|6|$]]|$M|W|O|X|2|Q|R|1G|S|@$U|1H|V|1I|Y|Z]]|T|@$U|1J|V|1K|M|1L]]|6|$]]|$M|10|O|11|2|12|R|1M|S|@]|T|@]|6|$13|14]]|$M|15|O|16|2|Q|R|1N|S|@]|T|@$U|1O|V|1P|M|1Q]]|6|$]]|$M|17|O|18|2|Q|R|1R|S|@]|T|@$U|1S|V|1T|M|1U]|$U|1V|V|1W|M|1X]|$U|1Y|V|1Z|M|20]]|6|$]]|$M|19|O|1A|2|Q|R|21|S|@]|T|@$U|22|V|23|M|24]]|6|$]]|$M|1B|O|-4|2|Q|R|25|S|@]|T|@]|6|$]]]]

<a href="https://www.nuget.org/packages/NLog.Web.AspNetCore/" rel="nofollow noreferrer">NLog.Web.AspNetCore</a> provides lots of layout renderers that can capture HttpRequest-context-properties for logging (Without needing to inject into NLog MDLC).

This will probe the HttpRequest-Header for the value <code>JSNLog-RequestId</code>, and if empty fallback to the AspNetCore-RequestId, and if also empty then fallback to <a href="https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.httpcontext.traceidentifier" rel="nofollow noreferrer">AspNetCore-TraceIdentifer</a> 

<pre><code>${aspnet-request:header=JSNLog-RequestId:whenEmpty=${mdlc:item=RequestId:whenEmpty=${aspnet-traceIdentifier}}}
</code></pre>

List of available <a href="https://nlog-project.org/config/?tab=layout-renderers&amp;search=package:nlog.web.aspnetcore" rel="nofollow noreferrer">${aspnet} Layout-renderers</a> 

NLog uses <a href="https://docs.microsoft.com/en-us/dotnet/api/system.threading.asynclocal-1" rel="nofollow noreferrer">AsyncLocal</a> on NetCore, and if you are using Microsoft Extension Logging (MEL), then you can use <a href="https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.ilogger.beginscope" rel="nofollow noreferrer">ILogger.BeginScope</a> to inject properties into <a href="https://github.com/NLog/NLog.Extensions.Logging/wiki/NLog-properties-with-Microsoft-Extension-Logging#beginscope" rel="nofollow noreferrer">NLog MDLC</a> (And clear when leaving scope)

NLog MDLC can also be filled using <a href="https://github.com/NLog/NLog/wiki/MDLC-Layout-Renderer#scoped-item" rel="nofollow noreferrer">MappedDiagnosticsLogicalContext.SetScoped</a> that also will clear when leaving using-scope.

Does Asp.Net Core preserve CallContext across requests?

We have a use case to attach contextual properties (username) to the thread, which can be pulled from our logging framework (NLog, <a href="https://github.com/NLog/NLog/wiki/MDLC-Layout-Renderer" rel="nofollow noreferrer">MDLC</a>). MDLC uses <code>CallContext</code> as far as I can tell.

We need each request to have clean contextual properties. Do we need to clear the CallContext at the beginning?

Does Asp.Net Core preserve CallContext across requests?

中间件

 Asp.Net核心是否跨请求保留CallContext？ 我们有一个将上下文属性(用户名)附加到线程的用例，它可以从我们的日志框架(NLog，MDLC)中提取出来。据我所知，MDLC使用CallContext。 我们需要每个请求都有干净的上下文属性。我们需要在开始时清除CallContext吗？ 

问Asp.Net核心是否跨请求保留CallContext？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Asp.Net核心是否跨请求保留CallContext？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Asp.Net核心是否跨请求保留CallContext？
EN