Semantic Logging Application Block (SLAB) alternatives and similar packages
Based on the "Logging" category
A no-nonsense logging library for the NoSQL era. Combines the best of traditional and structured diagnostic logging in an easy-to-use package.
The Apache log4net library is a tool to help the programmer output log statements to a variety of output targets
Error handler used for the Stack Exchange network
Logary is a high performance, multi-target logging, metric, tracing and health-check library for mono and .Net. .Net's answer to DropWizard. Supports many targets, built for micro-services.
Elmah for MVC
.NET SDK for Sentry Open-source error tracking that helps developers monitor and fix crashes in real time..
Official ELMAH site
A zero-allocation .NET logging library
Tracing rewriter using Fody
Generic file logger for .NET Core (FileLoggerProvider) with minimal dependencies
Open source nlog viewer for Windows
ELMAH error logger for sending errors to elmah.io.
Full fledged, async, .Net Pushover client
NLog.Targets.Pushover is a custom target for NLog enabling you to send logging messages to the Pushover service
Centralized .NET logging and monitoring
Logs errors. Includes useful diagnostic info like stack trace, session, release, etc. Has a free tier. [Free for OSS][$]
Extends the inbuilt features of System.Diagnostics namespace to provide flexible logging
BugGuardian: Easily track you exceptions on Azure DevOps and TFS
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of Semantic Logging Application Block (SLAB) or a related project?
: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?
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 each release are available.