DevInstance.LogScope
10.1.0
dotnet add package DevInstance.LogScope --version 10.1.0
NuGet\Install-Package DevInstance.LogScope -Version 10.1.0
<PackageReference Include="DevInstance.LogScope" Version="10.1.0" />
<PackageVersion Include="DevInstance.LogScope" Version="10.1.0" />
<PackageReference Include="DevInstance.LogScope" />
paket add DevInstance.LogScope --version 10.1.0
#r "nuget: DevInstance.LogScope, 10.1.0"
#:package DevInstance.LogScope@10.1.0
#addin nuget:?package=DevInstance.LogScope&version=10.1.0
#tool nuget:?package=DevInstance.LogScope&version=10.1.0
LogScope.NET: Logging, tracing and profiling
LogScope.NET is a lightweight logging framework designed for tracing, profiling, and logging critical parts of your code. It can seamlessly integrate with popular logging libraries like Log4Net and NLog.
The framework revolves around the concept of a "scope," which can represent a method or a specific part of it. The implementation is based on the IDisposable interface, where calling Dispose method marks the end of the scope.
Additionally, it offers more streamlined coding and shorter lines of code compared to the conventional logging APIs.
Here's an example that illustrates this approach:
class TestClass
{
IScopeLog classScope;
public TestClass(IScopeManager manager)
{
classScope = manager.CreateLogger(this);
}
public void MethodA()
{
using (var methodScope = classScope.DebugScope())
{
methodScope.D("Wait for 200 msec");
Thread.Sleep(200);
methodScope.D("Done.");
using (var aScope = methodScope.DebugScope("a-scope"))
{
aScope.D("Inside of a scope");
}
MethodB();
}
}
private void MethodB()
{
using (var methodScope = classScope.DebugScope())
{
methodScope.D("Inside of method B scope");
Thread.Sleep(200);
}
}
}
Result:
21-01-29 23:07:24--> TestClass:MethodA
21-01-29 23:07:24 TestClass:MethodA:Wait for 200 msec
21-01-29 23:07:25 TestClass:MethodA:Done.
21-01-29 23:07:25--> TestClass:MethodA:a-scope
21-01-29 23:07:25 TestClass:MethodA:a-scope:Inside of a scope
21-01-29 23:07:25<-- TestClass:MethodA:a-scope, time:2.1252 msec
21-01-29 23:07:25--> TestClass:MethodB
21-01-29 23:07:25 TestClass:MethodB:Inside of method B scope
21-01-29 23:07:25<-- TestClass:MethodB, time:212.748 msec
21-01-29 23:07:25<-- TestClass:MethodA, time:480.5525 msec
Setup
LogScope packages are available on NuGet:
- DevInstance.LogScope - Core library (.NET 10)
- DevInstance.LogScope.NET - .NET 10+ with DI support
- DevInstance.LogScope.Extensions.MicrosoftLogger - Microsoft.Extensions.Logging integration
- DevInstance.LogScope.Extensions.SerilogLogger - Serilog integration
Add the package reference to your project:
CLI:
# Core library (.NET 10)
dotnet add package DevInstance.LogScope
# .NET 10+ with dependency injection
dotnet add package DevInstance.LogScope.NET
# Microsoft Logging extension
dotnet add package DevInstance.LogScope.Extensions.MicrosoftLogger
# Serilog extension
dotnet add package DevInstance.LogScope.Extensions.SerilogLogger
Package Manager:
# Core library (.NET 10)
Install-Package DevInstance.LogScope
# .NET 10+ with dependency injection
Install-Package DevInstance.LogScope.NET
# Microsoft Logging extension
Install-Package DevInstance.LogScope.Extensions.MicrosoftLogger
# Serilog extension
Install-Package DevInstance.LogScope.Extensions.SerilogLogger
Initialization
With Dependency Injection
If your application uses dependency injection, call the AddConsoleScopeLogging extension method:
public void ConfigureServices(IServiceCollection services)
{
services.AddConsoleScopeLogging(LogLevel.DEBUG);
}
Console Application (without DI)
For console applications, instantiate using DefaultScopeLogFactory directly:
var manager = DefaultScopeLogFactory.CreateConsoleLogger(LogLevel.DEBUG);
With Microsoft.Extensions.Logging
For integration with Microsoft's logging framework:
public void ConfigureServices(IServiceCollection services)
{
services.AddMicrosoftScopeLogging(LogLevel.DEBUG, "MyApp");
}
With Serilog
For integration with Serilog, using the global Log.Logger:
public void ConfigureServices(IServiceCollection services)
{
services.AddSerilogScopeLogging(LogLevel.DEBUG);
}
Or with a custom Serilog logger instance:
var serilogLogger = new LoggerConfiguration()
.MinimumLevel.Verbose()
.WriteTo.Console()
.CreateLogger();
services.AddSerilogScopeLogging(serilogLogger, LogLevel.DEBUG);
For console applications without DI, use the factory directly:
var manager = SerilogLogProviderFactory.CreateManager(
LogLevel.DEBUG,
Log.Logger,
new DefaultFormattersOptions { ShowTimestamp = true });
Message Templates
LogScope supports Serilog-style structured message templates. Placeholders in the template string are replaced with argument values in order:
log.I("Processed {Count} items in {Elapsed} ms", count, elapsed);
// Output: Processed 5 items in 120 ms
Format Specifiers
Apply .NET format strings using the {Name:format} syntax:
log.I("Elapsed: {Elapsed:000} ms", 34);
// Output: Elapsed: 034 ms
log.I("Date: {Date:yyyy-MM-dd}", DateTime.Now);
// Output: Date: 2026-02-26
Destructuring
Use the @ operator to destructure objects into their properties or enumerate collections:
log.I("Position: {@Pos}", new { Latitude = 25, Longitude = 134 });
// Output: Position: { Latitude: 25, Longitude: 134 }
log.I("Items: {@Items}", new List<int> { 1, 2, 3 });
// Output: Items: [1, 2, 3]
Escaped Braces
Use {{ and }} to output literal braces:
log.I("Value is {{not a placeholder}}");
// Output: Value is {not a placeholder}
Template overloads are available for all log levels: T(), D(), I(), W(), and E().
Log Levels
LogScope supports the following log levels:
| Level | Description |
|---|---|
NOLOG |
Disable logging |
ERROR |
Error messages only |
WARNING |
Warnings and errors |
INFO |
Informational messages |
DEBUG |
Debug messages (verbose) |
Documentation
See more information about the API: https://devinstance.net/engineering/logscope
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- No dependencies.
NuGet packages (6)
Showing the top 5 NuGet packages that depend on DevInstance.LogScope:
| Package | Downloads |
|---|---|
|
DevInstance.LogScope.Extensions.MicrosoftLogger
Microsoft logging extension integration with the LogScope. Read more: https://devinstance.net/engineering/logscope |
|
|
DevInstance.BlazorToolkit
BlazorToolkit is a comprehensive set of tools designed to enhance the development of Blazor applications. It provides a suite of utilities and services that streamline common tasks, allowing developers to focus on building rich, interactive web applications. |
|
|
DevInstance.Timelines.Blazor
Timelines is a chart library to help visualizing timelines and report for nocrast.com. This is still a working in progress and early version. |
|
|
DevInstance.LogScope.NET
.NET logging extension integration with the LogScope. LogScope implements simple logging framework for tracing, profiling and logging methods and critical parts of the code. LogScope is not yet another logger. It is an extension of existing logging libraries that provides alternative way of logging and measuring a performance of critical parts of code. It also helps building a cleaner picture of executing asynchronous calls. The whole idea is based on a “scope”. Scope can be method or a specific part of it. The implementation is based on IDisposable where calling Dispose ends the scope. Quick introduction: https://devinstance.net/blog/introducing-logscope Documentation: http://logscope.devinstance.net |
|
|
DevInstance.Timelines
Timelines is a chart library to help visualizing timelines and report for nocrast.com. This is still a working in progress and early version. |
GitHub repositories
This package is not used by any popular GitHub repositories.
Release notes for 10.1.0:
- Message Templates: now LogScope supports Serilog-style structured message templates
Release notes for 10.0.0:
- Migrated to .NET10;
Release notes for 1.4.2:
- Some performance improvements of the scope logging;
Release notes for 1.4.1:
- Added ability to track scope instance using 'Scope.Id";