nuget reorganization

This commit is contained in:
master
2025-11-18 23:45:25 +02:00
parent 77cee6a209
commit d3ecd7f8e6
7712 changed files with 13963 additions and 10007504 deletions

View File

@@ -1,5 +0,0 @@
{
"version": 2,
"contentHash": "B/X+wAfS7yWLVOTD83B+Ip9yl4MkhioaXj90JSoWi1Ayi8XHepEnsBdrkojg08eodCnmOKmShFUN2GgEc6c0CQ==",
"source": "https://api.nuget.org/v3/index.json"
}

View File

@@ -1,292 +0,0 @@
# Serilog.AspNetCore [![Build status](https://ci.appveyor.com/api/projects/status/4rscdto23ik6vm2r/branch/dev?svg=true)](https://ci.appveyor.com/project/serilog/serilog-aspnetcore/branch/dev) [![NuGet Version](http://img.shields.io/nuget/v/Serilog.AspNetCore.svg?style=flat)](https://www.nuget.org/packages/Serilog.AspNetCore/) [![NuGet Prerelease Version](http://img.shields.io/nuget/vpre/Serilog.AspNetCore.svg?style=flat)](https://www.nuget.org/packages/Serilog.AspNetCore/)
Serilog logging for ASP.NET Core. This package routes ASP.NET Core log messages through Serilog, so you can get information about ASP.NET's internal operations written to the same Serilog sinks as your application events.
With _Serilog.AspNetCore_ installed and configured, you can write log messages directly through Serilog or any `ILogger` interface injected by ASP.NET. All loggers will use the same underlying implementation, levels, and destinations.
**.NET Framework** and .NET Core 2.x are supported by version 3.4.0 of this package. Recent versions of _Serilog.AspNetCore_ require .NET Core 3.x, .NET 5, or later.
### Instructions
**First**, install the _Serilog.AspNetCore_ [NuGet package](https://www.nuget.org/packages/Serilog.AspNetCore) into your app.
```shell
dotnet add package Serilog.AspNetCore
```
**Next**, in your application's _Program.cs_ file, configure Serilog first. A `try`/`catch` block will ensure any configuration issues are appropriately logged:
```csharp
using Serilog;
Log.Logger = new LoggerConfiguration()
.WriteTo.Console()
.CreateLogger();
try
{
Log.Information("Starting web application");
var builder = WebApplication.CreateBuilder(args);
builder.Host.UseSerilog(); // <-- Add this line
var app = builder.Build();
app.MapGet("/", () => "Hello World!");
app.Run();
}
catch (Exception ex)
{
Log.Fatal(ex, "Application terminated unexpectedly");
}
finally
{
Log.CloseAndFlush();
}
```
The `builder.Host.UseSerilog()` call will redirect all log events through your Serilog pipeline.
**Finally**, clean up by removing the remaining configuration for the default logger, including the `"Logging"` section from _appsettings.*.json_ files (this can be replaced with [Serilog configuration](https://github.com/serilog/serilog-settings-configuration) as shown in [the _Sample_ project](https://github.com/serilog/serilog-aspnetcore/blob/dev/samples/Sample/Program.cs), if required).
That's it! With the level bumped up a little you will see log output resembling:
```
[22:14:44.646 DBG] RouteCollection.RouteAsync
Routes:
Microsoft.AspNet.Mvc.Routing.AttributeRoute
{controller=Home}/{action=Index}/{id?}
Handled? True
[22:14:44.647 DBG] RouterMiddleware.Invoke
Handled? True
[22:14:45.706 DBG] /lib/jquery/jquery.js not modified
[22:14:45.706 DBG] /css/site.css not modified
[22:14:45.741 DBG] Handled. Status code: 304 File: /css/site.css
```
**Tip:** to see Serilog output in the Visual Studio output window when running under IIS, either select _ASP.NET Core Web Server_ from the _Show output from_ drop-down list, or replace `WriteTo.Console()` in the logger configuration with `WriteTo.Debug()`.
A more complete example, including `appsettings.json` configuration, can be found in [the sample project here](https://github.com/serilog/serilog-aspnetcore/tree/dev/samples/Sample).
### Request logging
The package includes middleware for smarter HTTP request logging. The default request logging implemented by ASP.NET Core is noisy, with multiple events emitted per request. The included middleware condenses these into a single event that carries method, path, status code, and timing information.
As text, this has a format like:
```
[16:05:54 INF] HTTP GET / responded 200 in 227.3253 ms
```
Or [as JSON](https://github.com/serilog/serilog-formatting-compact):
```json
{
"@t": "2019-06-26T06:05:54.6881162Z",
"@mt": "HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms",
"@r": ["224.5185"],
"RequestMethod": "GET",
"RequestPath": "/",
"StatusCode": 200,
"Elapsed": 224.5185,
"RequestId": "0HLNPVG1HI42T:00000001",
"CorrelationId": null,
"ConnectionId": "0HLNPVG1HI42T"
}
```
To enable the middleware, first change the minimum level for `Microsoft.AspNetCore` to `Warning` in your logger configuration or _appsettings.json_ file:
```csharp
.MinimumLevel.Override("Microsoft.AspNetCore", LogEventLevel.Warning)
```
Then, in your application's _Program.cs_, add the middleware with `UseSerilogRequestLogging()`:
```csharp
var app = builder.Build();
app.UseSerilogRequestLogging(); // <-- Add this line
// Other app configuration
```
It's important that the `UseSerilogRequestLogging()` call appears _before_ handlers such as MVC. The middleware will not time or log components that appear before it in the pipeline. (This can be utilized to exclude noisy handlers from logging, such as `UseStaticFiles()`, by placing `UseSerilogRequestLogging()` after them.)
During request processing, additional properties can be attached to the completion event using `IDiagnosticContext.Set()`:
```csharp
public class HomeController : Controller
{
readonly IDiagnosticContext _diagnosticContext;
public HomeController(IDiagnosticContext diagnosticContext)
{
_diagnosticContext = diagnosticContext ??
throw new ArgumentNullException(nameof(diagnosticContext));
}
public IActionResult Index()
{
// The request completion event will carry this property
_diagnosticContext.Set("CatalogLoadTime", 1423);
return View();
}
```
This pattern has the advantage of reducing the number of log events that need to be constructed, transmitted, and stored per HTTP request. Having many properties on the same event can also make correlation of request details and other data easier.
The following request information will be added as properties by default:
* `RequestMethod`
* `RequestPath`
* `StatusCode`
* `Elapsed`
You can modify the message template used for request completion events, add additional properties, or change the event level, using the `options` callback on `UseSerilogRequestLogging()`:
```csharp
app.UseSerilogRequestLogging(options =>
{
// Customize the message template
options.MessageTemplate = "Handled {RequestPath}";
// Emit debug-level events instead of the defaults
options.GetLevel = (httpContext, elapsed, ex) => LogEventLevel.Debug;
// Attach additional properties to the request completion event
options.EnrichDiagnosticContext = (diagnosticContext, httpContext) =>
{
diagnosticContext.Set("RequestHost", httpContext.Request.Host.Value);
diagnosticContext.Set("RequestScheme", httpContext.Request.Scheme);
};
});
```
### Two-stage initialization
The example at the top of this page shows how to configure Serilog immediately when the application starts. This has the benefit of catching and reporting exceptions thrown during set-up of the ASP.NET Core host.
The downside of initializing Serilog first is that services from the ASP.NET Core host, including the `appsettings.json` configuration and dependency injection, aren't available yet.
To address this, Serilog supports two-stage initialization. An initial "bootstrap" logger is configured immediately when the program starts, and this is replaced by the fully-configured logger once the host has loaded.
To use this technique, first replace the initial `CreateLogger()` call with `CreateBootstrapLogger()`:
```csharp
using Serilog;
using Serilog.Events;
Log.Logger = new LoggerConfiguration()
.MinimumLevel.Override("Microsoft", LogEventLevel.Information)
.Enrich.FromLogContext()
.WriteTo.Console()
.CreateBootstrapLogger(); // <-- Change this line!
```
Then, pass a callback to `UseSerilog()` that creates the final logger:
```csharp
builder.Host.UseSerilog((context, services, configuration) => configuration
.ReadFrom.Configuration(context.Configuration)
.ReadFrom.Services(services)
.Enrich.FromLogContext()
.WriteTo.Console());
```
It's important to note that the final logger **completely replaces** the bootstrap logger: if you want both to log to the console, for instance, you'll need to specify `WriteTo.Console()` in both places, as the example shows.
#### Consuming `appsettings.json` configuration
**Using two-stage initialization**, insert the `ReadFrom.Configuration(context.Configuration)` call shown in the example above. The JSON configuration syntax is documented in [the _Serilog.Settings.Configuration_ README](https://github.com/serilog/serilog-settings-configuration).
#### Injecting services into enrichers and sinks
**Using two-stage initialization**, insert the `ReadFrom.Services(services)` call shown in the example above. The `ReadFrom.Services()` call will configure the logging pipeline with any registered implementations of the following services:
* `IDestructuringPolicy`
* `ILogEventEnricher`
* `ILogEventFilter`
* `ILogEventSink`
* `LoggingLevelSwitch`
#### Enabling `Microsoft.Extensions.Logging.ILoggerProvider`s
Serilog sends events to outputs called _sinks_, that implement Serilog's `ILogEventSink` interface, and are added to the logging pipeline using `WriteTo`. _Microsoft.Extensions.Logging_ has a similar concept called _providers_, and these implement `ILoggerProvider`. Providers are what the default logging configuration creates under the hood through methods like `AddConsole()`.
By default, Serilog ignores providers, since there are usually equivalent Serilog sinks available, and these work more efficiently with Serilog's pipeline. If provider support is needed, it can be optionally enabled.
To have Serilog pass events to providers, **using two-stage initialization** as above, pass `writeToProviders: true` in the call to `UseSerilog()`:
```csharp
builder.Host.UseSerilog(
(hostingContext, services, loggerConfiguration) => /* snip! */,
writeToProviders: true)
```
### JSON output
The `Console()`, `Debug()`, and `File()` sinks all support JSON-formatted output natively, via the included _Serilog.Formatting.Compact_ package.
To write newline-delimited JSON, pass a `CompactJsonFormatter` or `RenderedCompactJsonFormatter` to the sink configuration method:
```csharp
.WriteTo.Console(new RenderedCompactJsonFormatter())
```
### Writing to the Azure Diagnostics Log Stream
The Azure Diagnostic Log Stream ships events from any files in the `D:\home\LogFiles\` folder. To enable this for your app, add a file sink to your `LoggerConfiguration`, taking care to set the `shared` and `flushToDiskInterval` parameters:
```csharp
Log.Logger = new LoggerConfiguration()
.MinimumLevel.Debug()
.MinimumLevel.Override("Microsoft", LogEventLevel.Information)
.Enrich.FromLogContext()
.WriteTo.Console()
// Add this line:
.WriteTo.File(
System.IO.Path.Combine(Environment.GetEnvironmentVariable("HOME"), "LogFiles", "Application", "diagnostics.txt"),
rollingInterval: RollingInterval.Day,
fileSizeLimitBytes: 10 * 1024 * 1024,
retainedFileCountLimit: 2,
rollOnFileSizeLimit: true,
shared: true,
flushToDiskInterval: TimeSpan.FromSeconds(1))
.CreateLogger();
```
### Pushing properties to the `ILogger<T>`
If you want to add extra properties to all log events in a specific part of your code, you can add them to the **`ILogger<T>`** in **Microsoft.Extensions.Logging** with the following code. For this code to work, make sure you have added the `.Enrich.FromLogContext()` to the `.UseSerilog(...)` statement, as specified in the samples above.
```csharp
// Microsoft.Extensions.Logging ILogger<T>
// Yes, it's required to use a dictionary. See https://nblumhardt.com/2016/11/ilogger-beginscope/
using (logger.BeginScope(new Dictionary<string, object>
{
["UserId"] = "svrooij",
["OperationType"] = "update",
}))
{
// UserId and OperationType are set for all logging events in these brackets
}
```
The code above results in the same outcome as if you would push properties in the **ILogger** in Serilog.
```csharp
// Serilog ILogger
using (logger.PushProperty("UserId", "svrooij"))
using (logger.PushProperty("OperationType", "update"))
{
// UserId and OperationType are set for all logging events in these brackets
}
```
### Versioning
This package tracks the versioning and target framework support of its (indirect) [_Microsoft.Extensions.Hosting_](https://nuget.org/packages/Microsoft.Extensions.Hosting) dependency.

View File

@@ -1,95 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2013/05/nuspec.xsd">
<metadata>
<id>Serilog.AspNetCore</id>
<version>8.0.1</version>
<authors>Microsoft,Serilog Contributors</authors>
<license type="expression">Apache-2.0</license>
<licenseUrl>https://licenses.nuget.org/Apache-2.0</licenseUrl>
<icon>icon.png</icon>
<readme>README.md</readme>
<projectUrl>https://github.com/serilog/serilog-aspnetcore</projectUrl>
<description>Serilog support for ASP.NET Core logging</description>
<tags>serilog aspnet aspnetcore</tags>
<repository type="git" url="https://github.com/serilog/serilog-aspnetcore" commit="68f2f3d41d4ff92e11107618625ec19b9a43e4e4" />
<dependencies>
<group targetFramework=".NETFramework4.6.2">
<dependency id="Microsoft.AspNetCore.Hosting.Abstractions" version="2.2.0" exclude="Build,Analyzers" />
<dependency id="Microsoft.AspNetCore.Http.Abstractions" version="2.2.0" exclude="Build,Analyzers" />
<dependency id="Microsoft.Extensions.DependencyInjection" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Microsoft.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog" version="3.1.1" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Hosting" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Formatting.Compact" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Settings.Configuration" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Console" version="5.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Debug" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.File" version="5.0.0" exclude="Build,Analyzers" />
</group>
<group targetFramework="net6.0">
<dependency id="Microsoft.Extensions.DependencyInjection" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Microsoft.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog" version="3.1.1" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Hosting" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Formatting.Compact" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Settings.Configuration" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Console" version="5.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Debug" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.File" version="5.0.0" exclude="Build,Analyzers" />
</group>
<group targetFramework="net7.0">
<dependency id="Microsoft.Extensions.DependencyInjection" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Microsoft.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog" version="3.1.1" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Hosting" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Formatting.Compact" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Settings.Configuration" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Console" version="5.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Debug" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.File" version="5.0.0" exclude="Build,Analyzers" />
</group>
<group targetFramework="net8.0">
<dependency id="Microsoft.Extensions.DependencyInjection" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Microsoft.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog" version="3.1.1" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Hosting" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Formatting.Compact" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Settings.Configuration" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Console" version="5.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Debug" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.File" version="5.0.0" exclude="Build,Analyzers" />
</group>
<group targetFramework=".NETStandard2.0">
<dependency id="Microsoft.AspNetCore.Hosting.Abstractions" version="2.2.0" exclude="Build,Analyzers" />
<dependency id="Microsoft.AspNetCore.Http.Abstractions" version="2.2.0" exclude="Build,Analyzers" />
<dependency id="Microsoft.Extensions.DependencyInjection" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Microsoft.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog" version="3.1.1" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Hosting" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Extensions.Logging" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Formatting.Compact" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Settings.Configuration" version="8.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Console" version="5.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.Debug" version="2.0.0" exclude="Build,Analyzers" />
<dependency id="Serilog.Sinks.File" version="5.0.0" exclude="Build,Analyzers" />
</group>
</dependencies>
<frameworkReferences>
<group targetFramework="net6.0">
<frameworkReference name="Microsoft.AspNetCore.App" />
</group>
<group targetFramework="net7.0">
<frameworkReference name="Microsoft.AspNetCore.App" />
</group>
<group targetFramework="net8.0">
<frameworkReference name="Microsoft.AspNetCore.App" />
</group>
<group targetFramework=".NETFramework4.6.2" />
<group targetFramework=".NETStandard2.0" />
</frameworkReferences>
</metadata>
</package>

Binary file not shown.

Before

Width:  |  Height:  |  Size: 20 KiB

View File

@@ -1,96 +0,0 @@
<?xml version="1.0"?>
<doc>
<assembly>
<name>Serilog.AspNetCore</name>
</assembly>
<members>
<member name="T:Serilog.AspNetCore.RequestLoggingOptions">
<summary>
Contains options for the <see cref="T:Serilog.AspNetCore.RequestLoggingMiddleware"/>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.MessageTemplate">
<summary>
Gets or sets the message template. The default value is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</summary>
<value>
The message template.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetLevel">
<summary>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/> based on the <see cref="T:Microsoft.AspNetCore.Http.HttpContext"/>, the number of
elapsed milliseconds required for handling the request, and an <see cref="T:System.Exception" /> if one was thrown.
The default behavior returns <see cref="F:Serilog.Events.LogEventLevel.Error"/> when the response status code is greater than 499 or if the
<see cref="T:System.Exception"/> is not null.
</summary>
<value>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/>.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.EnrichDiagnosticContext">
<summary>
A callback that can be used to set additional properties on the request completion event.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.Logger">
<summary>
The logger through which request completion events will be logged. The default is to use the
static <see cref="T:Serilog.Log"/> class.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.IncludeQueryInRequestPath">
<summary>
Include the full URL query string in the <c>RequestPath</c> property
that is attached to request log events. The default is <c>false</c>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetMessageTemplateProperties">
<summary>
A function to specify the values of the MessageTemplateProperties.
</summary>
</member>
<member name="M:Serilog.AspNetCore.RequestLoggingOptions.#ctor">
<summary>
Constructor
</summary>
</member>
<member name="T:Serilog.SerilogApplicationBuilderExtensions">
<summary>
Extends <see cref="T:Microsoft.AspNetCore.Builder.IApplicationBuilder"/> with methods for configuring Serilog features.
</summary>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.String)">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="messageTemplate">The message template to use when logging request completion
events. The default is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</param>
<returns>The application builder.</returns>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.Action{Serilog.AspNetCore.RequestLoggingOptions})">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="configureOptions">A <see cref="T:System.Action`1" /> to configure the provided <see cref="T:Serilog.AspNetCore.RequestLoggingOptions" />.</param>
<returns>The application builder.</returns>
</member>
</members>
</doc>

View File

@@ -1,96 +0,0 @@
<?xml version="1.0"?>
<doc>
<assembly>
<name>Serilog.AspNetCore</name>
</assembly>
<members>
<member name="T:Serilog.AspNetCore.RequestLoggingOptions">
<summary>
Contains options for the <see cref="T:Serilog.AspNetCore.RequestLoggingMiddleware"/>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.MessageTemplate">
<summary>
Gets or sets the message template. The default value is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</summary>
<value>
The message template.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetLevel">
<summary>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/> based on the <see cref="T:Microsoft.AspNetCore.Http.HttpContext"/>, the number of
elapsed milliseconds required for handling the request, and an <see cref="T:System.Exception" /> if one was thrown.
The default behavior returns <see cref="F:Serilog.Events.LogEventLevel.Error"/> when the response status code is greater than 499 or if the
<see cref="T:System.Exception"/> is not null.
</summary>
<value>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/>.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.EnrichDiagnosticContext">
<summary>
A callback that can be used to set additional properties on the request completion event.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.Logger">
<summary>
The logger through which request completion events will be logged. The default is to use the
static <see cref="T:Serilog.Log"/> class.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.IncludeQueryInRequestPath">
<summary>
Include the full URL query string in the <c>RequestPath</c> property
that is attached to request log events. The default is <c>false</c>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetMessageTemplateProperties">
<summary>
A function to specify the values of the MessageTemplateProperties.
</summary>
</member>
<member name="M:Serilog.AspNetCore.RequestLoggingOptions.#ctor">
<summary>
Constructor
</summary>
</member>
<member name="T:Serilog.SerilogApplicationBuilderExtensions">
<summary>
Extends <see cref="T:Microsoft.AspNetCore.Builder.IApplicationBuilder"/> with methods for configuring Serilog features.
</summary>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.String)">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="messageTemplate">The message template to use when logging request completion
events. The default is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</param>
<returns>The application builder.</returns>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.Action{Serilog.AspNetCore.RequestLoggingOptions})">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="configureOptions">A <see cref="T:System.Action`1" /> to configure the provided <see cref="T:Serilog.AspNetCore.RequestLoggingOptions" />.</param>
<returns>The application builder.</returns>
</member>
</members>
</doc>

View File

@@ -1,96 +0,0 @@
<?xml version="1.0"?>
<doc>
<assembly>
<name>Serilog.AspNetCore</name>
</assembly>
<members>
<member name="T:Serilog.AspNetCore.RequestLoggingOptions">
<summary>
Contains options for the <see cref="T:Serilog.AspNetCore.RequestLoggingMiddleware"/>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.MessageTemplate">
<summary>
Gets or sets the message template. The default value is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</summary>
<value>
The message template.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetLevel">
<summary>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/> based on the <see cref="T:Microsoft.AspNetCore.Http.HttpContext"/>, the number of
elapsed milliseconds required for handling the request, and an <see cref="T:System.Exception" /> if one was thrown.
The default behavior returns <see cref="F:Serilog.Events.LogEventLevel.Error"/> when the response status code is greater than 499 or if the
<see cref="T:System.Exception"/> is not null.
</summary>
<value>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/>.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.EnrichDiagnosticContext">
<summary>
A callback that can be used to set additional properties on the request completion event.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.Logger">
<summary>
The logger through which request completion events will be logged. The default is to use the
static <see cref="T:Serilog.Log"/> class.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.IncludeQueryInRequestPath">
<summary>
Include the full URL query string in the <c>RequestPath</c> property
that is attached to request log events. The default is <c>false</c>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetMessageTemplateProperties">
<summary>
A function to specify the values of the MessageTemplateProperties.
</summary>
</member>
<member name="M:Serilog.AspNetCore.RequestLoggingOptions.#ctor">
<summary>
Constructor
</summary>
</member>
<member name="T:Serilog.SerilogApplicationBuilderExtensions">
<summary>
Extends <see cref="T:Microsoft.AspNetCore.Builder.IApplicationBuilder"/> with methods for configuring Serilog features.
</summary>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.String)">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="messageTemplate">The message template to use when logging request completion
events. The default is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</param>
<returns>The application builder.</returns>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.Action{Serilog.AspNetCore.RequestLoggingOptions})">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="configureOptions">A <see cref="T:System.Action`1" /> to configure the provided <see cref="T:Serilog.AspNetCore.RequestLoggingOptions" />.</param>
<returns>The application builder.</returns>
</member>
</members>
</doc>

View File

@@ -1,96 +0,0 @@
<?xml version="1.0"?>
<doc>
<assembly>
<name>Serilog.AspNetCore</name>
</assembly>
<members>
<member name="T:Serilog.AspNetCore.RequestLoggingOptions">
<summary>
Contains options for the <see cref="T:Serilog.AspNetCore.RequestLoggingMiddleware"/>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.MessageTemplate">
<summary>
Gets or sets the message template. The default value is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</summary>
<value>
The message template.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetLevel">
<summary>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/> based on the <see cref="T:Microsoft.AspNetCore.Http.HttpContext"/>, the number of
elapsed milliseconds required for handling the request, and an <see cref="T:System.Exception" /> if one was thrown.
The default behavior returns <see cref="F:Serilog.Events.LogEventLevel.Error"/> when the response status code is greater than 499 or if the
<see cref="T:System.Exception"/> is not null.
</summary>
<value>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/>.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.EnrichDiagnosticContext">
<summary>
A callback that can be used to set additional properties on the request completion event.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.Logger">
<summary>
The logger through which request completion events will be logged. The default is to use the
static <see cref="T:Serilog.Log"/> class.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.IncludeQueryInRequestPath">
<summary>
Include the full URL query string in the <c>RequestPath</c> property
that is attached to request log events. The default is <c>false</c>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetMessageTemplateProperties">
<summary>
A function to specify the values of the MessageTemplateProperties.
</summary>
</member>
<member name="M:Serilog.AspNetCore.RequestLoggingOptions.#ctor">
<summary>
Constructor
</summary>
</member>
<member name="T:Serilog.SerilogApplicationBuilderExtensions">
<summary>
Extends <see cref="T:Microsoft.AspNetCore.Builder.IApplicationBuilder"/> with methods for configuring Serilog features.
</summary>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.String)">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="messageTemplate">The message template to use when logging request completion
events. The default is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</param>
<returns>The application builder.</returns>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.Action{Serilog.AspNetCore.RequestLoggingOptions})">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="configureOptions">A <see cref="T:System.Action`1" /> to configure the provided <see cref="T:Serilog.AspNetCore.RequestLoggingOptions" />.</param>
<returns>The application builder.</returns>
</member>
</members>
</doc>

View File

@@ -1,96 +0,0 @@
<?xml version="1.0"?>
<doc>
<assembly>
<name>Serilog.AspNetCore</name>
</assembly>
<members>
<member name="T:Serilog.AspNetCore.RequestLoggingOptions">
<summary>
Contains options for the <see cref="T:Serilog.AspNetCore.RequestLoggingMiddleware"/>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.MessageTemplate">
<summary>
Gets or sets the message template. The default value is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</summary>
<value>
The message template.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetLevel">
<summary>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/> based on the <see cref="T:Microsoft.AspNetCore.Http.HttpContext"/>, the number of
elapsed milliseconds required for handling the request, and an <see cref="T:System.Exception" /> if one was thrown.
The default behavior returns <see cref="F:Serilog.Events.LogEventLevel.Error"/> when the response status code is greater than 499 or if the
<see cref="T:System.Exception"/> is not null.
</summary>
<value>
A function returning the <see cref="T:Serilog.Events.LogEventLevel"/>.
</value>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.EnrichDiagnosticContext">
<summary>
A callback that can be used to set additional properties on the request completion event.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.Logger">
<summary>
The logger through which request completion events will be logged. The default is to use the
static <see cref="T:Serilog.Log"/> class.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.IncludeQueryInRequestPath">
<summary>
Include the full URL query string in the <c>RequestPath</c> property
that is attached to request log events. The default is <c>false</c>.
</summary>
</member>
<member name="P:Serilog.AspNetCore.RequestLoggingOptions.GetMessageTemplateProperties">
<summary>
A function to specify the values of the MessageTemplateProperties.
</summary>
</member>
<member name="M:Serilog.AspNetCore.RequestLoggingOptions.#ctor">
<summary>
Constructor
</summary>
</member>
<member name="T:Serilog.SerilogApplicationBuilderExtensions">
<summary>
Extends <see cref="T:Microsoft.AspNetCore.Builder.IApplicationBuilder"/> with methods for configuring Serilog features.
</summary>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.String)">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="messageTemplate">The message template to use when logging request completion
events. The default is
<c>"HTTP {RequestMethod} {RequestPath} responded {StatusCode} in {Elapsed:0.0000} ms"</c>. The
template can contain any of the placeholders from the default template, names of properties
added by ASP.NET Core, and names of properties added to the <see cref="T:Serilog.IDiagnosticContext"/>.
</param>
<returns>The application builder.</returns>
</member>
<member name="M:Serilog.SerilogApplicationBuilderExtensions.UseSerilogRequestLogging(Microsoft.AspNetCore.Builder.IApplicationBuilder,System.Action{Serilog.AspNetCore.RequestLoggingOptions})">
<summary>
Adds middleware for streamlined request logging. Instead of writing HTTP request information
like method, path, timing, status code and exception details
in several events, this middleware collects information during the request (including from
<see cref="T:Serilog.IDiagnosticContext"/>), and writes a single event at request completion. Add this
in <c>Startup.cs</c> before any handlers whose activities should be logged.
</summary>
<param name="app">The application builder.</param>
<param name="configureOptions">A <see cref="T:System.Action`1" /> to configure the provided <see cref="T:Serilog.AspNetCore.RequestLoggingOptions" />.</param>
<returns>The application builder.</returns>
</member>
</members>
</doc>

View File

@@ -1 +0,0 @@
bfMahsQW22+8L1ur3OuBWIBi+BY82q/9rwm7CZuFiPNV7Ng6S/mjUbU/uxc1vHsvJ4yvrhwTf6TjUHCFR2FWXA==