UseSerilogRequestLogging is not present in the Nuget package v2.1.1
See original GitHub issueI have looked at your samples where you demonstrate the use of app.UseSerilogRequestLogging();
although it uses the Serilog.AspNetCore
project directly. As soon as you use the Nuget package it can no longer find the extension method.
Can you please verify that the extension method is correctly built into your nuget package please?
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Reducing log verbosity with Serilog RequestLogging
In this post I describe how you can use Serilog.AspNetCore to reduce the number of logs generated by every request in ASP.NET Core...
Read more >serilog-aspnetcore/ at dev
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...
Read more >Can't install NuGet package Serilog.Sinks.
Hi this worked for me nugget install Serilog.Sinks.
Read more >Setting up Serilog in ASP.NET Core 3
I tend not to want request logging for static files, so I add UseSerilogRequestLogging() later in the pipeline, as shown above. The resulting ......
Read more >Serilog.Extensions.Logging 7.0.0
NET Core 1.0, 1.1 and Default Provider Integration. The package implements AddSerilog() on ILoggingBuilder and ILoggerFactory to enable the Serilog provider ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Alright, the readme states it like it’s available for use now, which is a bit confusing. Maybe this could use some clarification so other people don’t stumble into the same misunderstanding.
@StefanFrederiksen I’ve made some subtle README tweaks that should help with this