rebus-org / rebus.microsoft.extensions.logging

:bus: Microsoft Logging Extensions integration for Rebus

Rebus.Microsoft.Extensions.Logging

Provides a Microsoft Extensions Logging logging integration for Rebus.

---

Like this:

var loggerFactory = new LoggerFactory()
	.AddConsole();

Configure.With(...)
	.Logging(l => l.MicrosoftExtensionsLogging(loggerFactory))
	.Transport(t => t.Use(...))
	.(...)
	.Start();

or like this:

var logger = new LoggerFactory()
	.AddConsole()
	.CreateLogger<Program>();

Configure.With(...)
	.Logging(l => l.MicrosoftExtensionsLogging(logger))
	.Transport(t => t.Use(...))
	.(...)
	.Start();

rebus.microsoft.extensions.logging's Issues

Add resolver function support to allow resolving from an IoC container

I was looking at integrating Rebus with App Insights. But I'm struggling a bit with the ILoggerFactory reference.
We don't add the LoggerFactory directly to the container at the moment. So we don't have a reference when configuring the container. Adding support for passing in a resolver function would allow us to use the DI container.

Or is this a daft idea and should I just manually create a LoggerFactory instance?

How to set log levels?

Is there any way I can configure the log levels? I don't want my application insights to be flooded with trace messages.

net6 support for Rebus.Microsoft.Extensions.Logging

Got conflicts when using

Add support for net6 in Rebus.Microsoft.Extensions.Logging.
Add support for Microsoft.Extensions.Logging v6 (low) in Rebus.Microsoft.Extensions.Logging

PR:
Pull req

.NET 6/7 and .NET Standard 2.1: Resolving Microsoft.Extensions.Logging Versions

Hi!

I am getting in some projects version mismatches when using .NET 6/7 with .NET Standard 2.1 as class libraries:

warning NU1608: Detected package version outside of dependency constraint: 
Rebus.Microsoft.Extensions.Logging 3.0.0 requires microsoft.extensions.logging (>= 6.0.0 && < 7.0.0) 
but version Microsoft.Extensions.Logging 7.0.0 was resolved. [TargetFramework=net6.0]

warning NU1608: Detected package version outside of dependency constraint: 
Rebus.Microsoft.Extensions.Logging 3.0.0 requires microsoft.extensions.logging (>= 6.0.0 && < 7.0.0) 
but version Microsoft.Extensions.Logging 7.0.0 was resolved. [TargetFramework=net7.0]

Is there an incompatibility of netstandard with microsoft.extensions.logging that prevents us from just using the package without version constraints? if so, is there a workaround?

<ItemGroup Condition="'$(TargetFramework)' == 'netstandard2.0'">
		<PackageReference Include="microsoft.extensions.logging" Version="[6,7)" />
	</ItemGroup>
	<ItemGroup Condition="'$(TargetFramework)' == 'net7.0'">
		<PackageReference Include="microsoft.extensions.logging" Version="[7,8)" />
	</ItemGroup>

Thank you!

Release version

Is there a plan to publish a release version of this library?
If not, what would be the preferred way to hook into the default netcore abstractions?

Microsoft.Extensions.Logging v2.2?

Is there a reason why this project is referencing version 2.2.0 of Microsoft.Extensions.Logging? Since .NET Core 2.1 is the current LTS version (until 3.1 is released), I assume other development teams out there have the same restrictions as us, where the 2.2 runtime is not installed on production servers.

Even though it might work referencing this project from an application using target framework netcoreapp2.1, I'd feel safer if this project were using version 2.1 (or even 2.0) of Microsoft.Extensions.Logging. Does not seem like this project requires any specific features of version 2.2.0?