Semantic Logging Application Block (SLAB) alternatives and similar packages
Based on the "Logging" category.
Alternatively, view Semantic Logging Application Block (SLAB) alternatives based on common mentions on social networks and blogs.
-
NLog
NLog - Advanced and Structured Logging for Various .NET Platforms -
Serilog
Simple .NET logging with fully-structured events -
Log4Net
Mirror of This is the Apache log4net logging project git repository. -
StackExchange.Exceptional
Error handler used for the Stack Exchange network -
-
Logary
Logs and metrics are one! Professional logging, metrics and analytics for your apps. -
ELMAH
Error Logging Modules & Handlers for ASP.NET -
Elmah MVC
Painless integration of ELMAH into ASP.NET MVC application -
ZeroLog
A high-performance, zero-allocation .NET logging library. -
-
NReco.Logging.File
Generic file logger for .NET Core (FileLoggerProvider) with minimal dependencies -
Sejil
Capture, view and filter your ASP.net core log events right from your app -
Logazmic
Windows log viewer for log4j -
ULogViewer
Cross-Platform Universal Log Viewer. -
elmah.io
ELMAH error logger for sending errors to elmah.io. -
NPushOver
Full fledged, async, .Net Pushover client -
Serilog.Sinks.Notepad
A Serilog sink that writes log events to Notepad as text or JSON -
BugGuardian
BugGuardian: Easily track you exceptions on Azure DevOps and TFS -
Serilog.Sinks.ExcelDnaLogDisplay
A Serilog sink that writes events to Excel-DNA LogDisplay -
ExcelDna.Diagnostics.Serilog
Integrate Excel-DNA Diagnostic Logging with your Serilog logging pipeling within your Excel-DNA add-in -
NLog.Targets.Pushover
NLog.Targets.Pushover is a custom target for NLog enabling you to send logging messages to the Pushover service -
Ac682.Extensions.Logging.Console
a provider for Microsoft.Extensions.Logging which provides a colored console logger. -
Essential Diagnostics
Extends the inbuilt features of System.Diagnostics namespace to provide flexible logging -
BugSnag
Logs errors. Includes useful diagnostic info like stack trace, session, release, etc. Has a free tier. [Free for OSS][$]
Less time debugging, more time building
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Semantic Logging Application Block (SLAB) or a related project?
|
Static code analysis for 29 languages.
sponsored
www.sonarqube.org
|
Popular Comparisons
-
Semantic Logging Application Block (SLAB)vsSerilog
-
Semantic Logging Application Block (SLAB)vsLog4Net
-
Semantic Logging Application Block (SLAB)vsNLog
-
Semantic Logging Application Block (SLAB)vsNLog.Targets.Pushover
-
Semantic Logging Application Block (SLAB)vsELMAH
|
SaaSHub - Software Alternatives and Reviews
sponsored
www.saashub.com
|
README
:warning: This project is no longer under development. A possible alternative, depending on use case, is Microsoft.Diagnostic.EventFlow. :warning:
What is Semantic Logging?
Semantic Logging (formerly know at the Semantic Logging Application Block or SLAB) is designed by the patterns & practices team to help .NET developers move from the unstructured logging approach towards the strongly-typed (semantic) logging approach, making it easier to consume logging information, especially when there is a large volume of log data to be analyzed. When used out-of-process, Semantic Logging uses Event Tracing for Windows (ETW), a fast, lightweight, strongly typed, extensible logging system that is built into the Windows operating system.
Semantic Logging enables you to use the EventSource class and semantic log messages in your
applications without moving away from the log formats you are familiar with (such as database, text
file, Azure table storage). Also, you do not need to commit to how you consume events when developing
business logic; you have a unified application-specific API for logging and then you can decide later
whether you want those events to go to ETW or alternative destinations.
How do I use Semantic Logging?
Official releases are available via NuGet. You can also head to msdn.com for additional information, documentation, videos, and hands-on labs.
Building
To build the solution, run msbuild.exe from the project’s build folder. You'll need to use the
Visual Studio Developer Command Prompt. Some of the unit tests require a SQL database.
How do I contribute?
Please see CONTRIBUTING.md for more details.
Release notes
Release notes each release are available.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.