Found 133 packages
Provides the System.Diagnostics.EventLog class, which allows the applications to use the Windows event log service. Commonly Used Types: System.Diagnostics.EventLog
Windows Event Log logger provider implementation for Microsoft.Extensions.Logging.
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 6, 7, 8, 9 and 10 - .NET Standard 2.0 and 2.1 - .NET Framework 3.5 - 4.8 - Xamarin Android + iOS (.NET Standard) - Mono 4 For integrating NLog with Microsoft.Extensions.Logging, check: https://www.nuget.org/packages/NLog.Extensions.Logging For using NLog with ASP.NET Core, check: https://www.nuget.org/packages/NLog.Web.AspNetCore
Serilog event sink that writes to the Windows Event Log.
NLog.WindowsEventLog provides access to the EventLog-target for NetStandard
Reporting interface for the firewall and the windows to support structured logging to the windows EventLog. The Package extends the reporting functionality to NuGet package Walter.Web.Firewall and is easily activated by dependency injection during service configuration services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey , domainName: new Uri("https://www.your-domain.com", UriKind.Absolute) , options => { //your firewall settings }).UseEventLogLogging(options=>{ options.LogName = "FireWall"; options.SourceName = "www.your-domain.com"; }); More information on how to use this Add-On is available in this manual https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf
Windows Event Log logger provider implementation for Microsoft.Extensions.Logging.
This package exposes an enhanced developer experience for coding against the Microsoft.Diagnostics.Tracing.EventSource (including build time validation). Microsoft.Diagnostics.Tracing.EventSource allows for firing ETW events from managed code. It enables defining a strongly typed specification of an ETW provider that can be called by managed code. The EventSource class is also included in the .NET Framework. This package provides a newer version that has more features. It is meant to be used as a stop gap until those features it contains are ported to System.Diagnostics.Tracing.EventSource. For more details, have a look at http://msdn.microsoft.com/en-us/library/system.diagnostics.tracing.eventsource.aspx. New features: - ETW channel support - Support for static registration Supported Platforms: - .NET Framework 3.5 - .NET Framework 4.0 - .NET Framework 4.5 - Windows Store apps - Windows Phone App 8.1
Provides EventLog logging integration for other ServiceStack projects
Log Audit.NET events to the Windows EventLog when targeting net standard
Methods to log text to a file
Interfaced wrappers around System Diagnostics.
Simplifies the use of Microsoft.Extensions.Logging.EventLog.
This component adds support for Almanac to format and persist its entries into the Microsoft Windows Event Log. Almanac is a flexible logging mechanism that routes log entries by its type to different destinations like email, text and XML files. Almanac is also great to keep a record of your user actions relevant for auditable purposes. KEYSTONE is a modern, multi-paradigm, data-centric software development framework. Visit http://www.keystoneframework.com for more details.
Provides event publisher implementation for entity changes
The CrispyWaffle EventLog bridge package
.Net Standard 2.0 compatible Log4Net appenders
EventLog Persistence with Entity Framework
A base class library for logging application events.
EventLogs for integration events