Logging

A simple logging abstraction. You don't have the option of using immediate-mode logging, so you never accidentally kill performance.

Logging infrastructure default implementation for Microsoft.Extensions.Logging.

Common.Logging library bindings for Log4Net 1.2.10 logging framework.

Console logger implementation.

Common.Logging library bindings for Log4Net 2.0.8 logging framework.

Common.Logging library bindings for NLog 3.2 logging framework.

This package provides a set of Logging Singleton helpers and extension methods used to accelerate development.

Common.Logging library bindings for Log4Net 1.2.15 logging framework.

The Relativity logging framework .NET package.

Common.Logging.Portable contains the portable (PCL) implementation of the common.logging library which introduces a simple abstraction to allow you to select a specific logging implementation at runtime.

Provides base interfaces for more robust Prism Logging.

Writes MySqlConnector logging output to Microsoft.Extensions.Logging with one line of code.

Microsoft Extension Logging implementation for ASP.NET Core Blazor.

This package provides a set of Logging helpers and extension methods used to accelerate development.

Logging helper slots for Magic, allowing you to inject your own logging implementation, giving you the ability to create log entries from Hyperlambda. To use package go to https://polterguy.github.io

log4net is a tool to help the programmer output log statements to a variety of output targets. In case of problems with an application, it is helpful to enable logging so that the problem can be located. With log4net it is possible to enable logging at runtime without modifying the application binary. The log4net package is designed so that log statements can remain in shipped code without incurring a high performance cost. It follows that the speed of logging (or rather not logging) is crucial. At the same time, log output can be so voluminous that it quickly becomes overwhelming. One of the distinctive features of log4net is the notion of hierarchical loggers. Using these loggers it is possible to selectively control which log statements are output at arbitrary granularity. log4net is designed with two distinct goals in mind: speed and flexibility

Core library for ELMAH (Error Logging Modules and Handlers) without any configuration.

ELMAH with initial configuration for getting started quickly. ELMAH (Error Logging Modules and Handlers) is an application-wide error logging facility that is completely pluggable. It can be dynamically added to a running ASP.NET web application, or even all ASP.NET web applications on a machine, without any need for re-compilation or re-deployment.

Package Description

Logging.Memory allows write log to memory

Simple .NET logging with fully-structured events

Dolittle is a platform designed to build Line of Business applications without sacrificing architectural quality, code quality or scalability.

A bridge between the old and the new: Simple Common Logging Adapter for Serilog NoSQL Logging.

See more at https://github.com/KolibreCredit/KC.Foundation .

NLog is a logging platform for .NET with rich log routing and management capabilities. NLog supports traditional logging, structured logging and the combination of both. Supported platforms: - .NET 5, 6, 7, 8 and 9 - .NET Core 1, 2 and 3 - .NET Standard 1.3+ and 2.0+ - .NET Framework 3.5 - 4.8 - Xamarin Android + iOS (.NET Standard) - Mono 4 For ASP.NET Core, check: https://www.nuget.org/packages/NLog.Web.AspNetCore

Common.Logging library bindings for NLog 4.0 logging framework.

Generic logging interface for class libraries.

Salient.ReflectiveLoggingAdapter

A general purpose logging library.

Unofficial Castle Windsor on dotnet core

Sitecore Diagnostics Tool Logging abstraction

.NET client for communicating with the elmah.io REST API

Adds support for adding logging to the hosted application by convention.

Logging Abstractor is a library for .NET that allows you to swap out logging providers with ease.

Contains simple ILogger and ILogManager interfaces.

The Semantic Logging Application Block provides a set of destinations (sinks) to persist application events published using a subclass of the EventSource class from the System.Diagnostics.Tracing namespace. Sinks include Azure table storage, SQL Server databases, file, console and rolling files with several formats and you can extend the block by creating your own custom formatters and sinks. The console sink is part of this nuget package. Other Sinks mentioned above are available as separate nuget packages. For the sinks that can store structured data, the block preserves the full structure of the event payload in order to facilitate analysing or processing the logged data. This library contains a class library that targets .Net Core 2.0 & .Net Standard 2.0.

Serilog support for ASP.NET Core logging

Common.Logging library bindings for NLog 4.4.12 logging framework.

Provides common logging abstractions and a basic networking logger for sending ILoggerFacade logs to a TCP/UDP server

Utility library for logging

Write RawRabbit's logs with Serilog

Supplemental data access object based loggers for Bam

Steeltoe library for enabling dynamic management of Serilog

ELMAH with configuration for getting started quickly on a Microsoft SQL Server (2000 or later) database as the error log. NB requires manual configuration.

The Semantic Logging Application Block provides a set of destinations to persist events published by a subclass of EventSource, This add-on packages adds support to persisting log entries in Azure table storage.

The EventSource Analyzer is part of the Semantic Logging Application Block. It can be incorporated into your automated tests to help validate your EventSource instances.

模块核心库

[DEPRECATED] Please install the Exceptionless package instead.

Connects NHibernate logging infrastructure to Common.Logging.

General base interfaces and classes for logging