Found 224 packages
Provides the System.Diagnostics.EventLog class, which allows the applications to use the Windows event log service. Commonly Used Types: System.Diagnostics.EventLog
Enrich Serilog log events with properties from System.Environment.
NLog Integration for Microsoft System.Diagnostics.DiagnosticSource and Activity TraceId / SpanId
EonaCat Alternate Logging system to log to the console or a file
Generate Audit Logs from file system events using a FileSystemWatcher
MetroLog is a lightweight logging framework designed for portable code and WinJS. Although the API is based on NLog and log4net, the intention is that it's a very basic logging system. This version targets .NET Core, .NET 4.5, Windows 8.1 (Windows Store apps), Windows Phone 8, WinPhone 8.1, WinJS, Xamarin.iOS, Xamarin.Android
MetroLog is a lightweight logging framework designed for .net 6. Although the API is based on NLog and log4net, the intention is that it's a very basic logging system. This version targets .net 6, which includes all platforms.
biz.dfch.PS.System.Logging ========================== Modules: biz.dfch.PS.System.Logging d-fens GmbH, General-Guisan-Strasse 6, CH-6300 Zug, Switzerland This PowerShell module contains Cmdlets that allow to perform logging from your PowerShell functions and code via the Apache Log4Net library. * You can also download this module via [NuGet](http://nuget.org) with [Install-Package biz.dfch.PS.System.Logging](https://www.nuget.org/packages/biz.dfch.PS.System.Logging/). * After downloading the package to a directory of your choice (_NOT_ the actual module directory) run the `install.ps1` script in the downloaded folder to copy the files to a directory inside `$ENV:PSModulePath`). * In case you already have a previous version of this module ( < 1.0.5) in a different module directory you have to remove that module manually. * In case you update the module in the same directory and the `log4net.dll` is still loaded you might have to restart all the PowerShell sessions to be able to overwrite the file. * In case you changed the log settings in `biz.dfch.PS.System.Logging.xml`, `Log4netConfiguration.xml` or `log4net.xml` you have to restore the changes as they will get overwritten. See http://d-fens.ch/2013/01/16/module-biz-dfch-ps-system-logging/ and the [Wiki](https://github.com/dfch/biz.dfch.PS.System.Logging/wiki) for more information.
LogSystem Appender for log4net - Seamlessly integrate your existing log4net applications with LogSystem distributed tracing and structured logging. Drop-in replacement requiring minimal configuration changes. Zero external dependencies except log4net. Supports .NET Framework 4.7.2+, .NET Standard 2.0, .NET Core 2.0+, .NET 6+, and .NET 8+.
log4net.ElasticSearch.Async is a log4net appender, based on log4net.ElasticSearch package, for easy logging of exceptions and messages to Elasticsearch indices. The main improvement over log4net.ElasticSearch is background/async logging based on producer-consumer pattern, automatically utilizing bulk API in case of log event bursts. Currently the package provides: - Background/Async logging based on producer-consumer pattern (non-blocking for main application thread) - Configurable exponential backoff retry policy for communication with ElasticSearch - Configurable buffer sizes with rolling buffer option (both general producer-consumer buffer and intermediate flush buffer) - External machine IP added to log events (if possible) - Skipping TLS certificate validation for ElasticSearch endpoint - Setting custom HTTP(S) proxy - Disabling system HTTP(S) proxy - Using custom ElasticSearch processing pipeline - Gzip HTTP compression - NET Standard 2.0 support
Enterprise-grade logging SDK for .NET with file-based logging, distributed tracing, ASP.NET Core middleware, Format methods (log4net-compatible), Logger API (Node.js-style), and ILogger integration. Zero external dependencies except Microsoft.Extensions.Logging.Abstractions. Supports .NET Framework 4.7.2+, .NET Standard 2.0, .NET Core 2.1+, .NET 6+, and .NET 8+.
K-Society Log is a centralized log system for .NET 6 and .NET 7 application
Logs
The easiest logging library to use to send log messages to syslog, the console, or the file system. It's. REALLY. Easy.
Event Tracing for Windows (ETW) is a powerful logging mechanism built into the Windows OS and is used extensively in Windows. You can also log ETW events yourself code using the System.Diagnostics.Tracing.EventSource class. The TraceEvent library conains the classes needed to control ETW providers (including .NET EventSources) and parse the events they emit. The library includes -- TraceEventSession which can enable ETW providers, -- EtwTraceEventSource which lets you read the stream of ETW events, and -- TraceLog which is is digested form of ETW events which include decoded stack traces associated with the events. See https://github.com/Microsoft/perfview/blob/master/documentation/TraceEvent/TraceEventLibrary.md for more.
An unofficial packaging of Log4Net to suit our needs -- specifically, allowing it's use on the .NET 3.5 *Client* framework, rather than .NET 2.0, which has a dependency on System.Web... Contact me know when an official package of NuGet with less framework requirements (don't hold your breath) becomes available so that I can remove this one. This package is based on the good investigation work done here: http://bit.ly/kcMjwv
Simple log system able to log to the file system, sql server or implement your own log repository very easy