Semantic Logging Application Block (SLAB) alternatives and similar packages
Based on the "Logging" category
-
Serilog
A no-nonsense logging library for the NoSQL era. Combines the best of traditional and structured diagnostic logging in an easy-to-use package. -
Log4Net
The Apache log4net library is a tool to help the programmer output log statements to a variety of output targets -
StackExchange.Exceptional
Error handler used for the Stack Exchange network -
Logary
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. -
Sentry
.NET SDK for Sentry Open-source error tracking that helps developers monitor and fix crashes in real time.. -
ZeroLog
A zero-allocation .NET logging library -
Rollbar.NET
Simplifies real-time remote error monitoring while using Rollbar.com. Open-source Rollbar Notifier SDK for any .NET-based technology stack. The SDK that can be used in any application built on the following .NET versions: .NET Core 2.0+, .NET Standard 2.0+, .NET Full Framework 4.5.1+, Mono, Xamarin, and, in general, any implementation of the .NET Standard 2.0+. It simplifies building data payloads based on exception data, tracing data, informational messages, and telemetry data and sends the payloads to the Rollbar API for remote monitoring and analysis of the hosting application's behavior. -
NReco.Logging.File
Generic file logger for .NET Core (FileLoggerProvider) with minimal dependencies -
Logazmic
Open source nlog viewer for Windows -
elmah.io
ELMAH error logger for sending errors to elmah.io. -
NPushOver
Full fledged, async, .Net Pushover client -
BugGuardian
BugGuardian: Easily track you exceptions on Azure DevOps and TFS -
Serilog.Sinks.Notepad
A Serilog sink that writes log events to Notepad as text or JSON -
ExcelDna.Diagnostics.Serilog
Integrate Excel-DNA Diagnostic Logging with your Serilog logging pipeling within your Excel-DNA add-in -
Serilog.Sinks.ExcelDnaLogDisplay
A Serilog sink that writes events to Excel-DNA LogDisplay -
NLog.Targets.Pushover
NLog.Targets.Pushover is a custom target for NLog enabling you to send logging messages to the Pushover service -
Loupe
Centralized .NET logging and monitoring -
BugSnag
Logs errors. Includes useful diagnostic info like stack trace, session, release, etc. Has a free tier. [Free for OSS][$] -
Essential Diagnostics
Extends the inbuilt features of System.Diagnostics namespace to provide flexible logging
SaaSHub - Software Alternatives and Reviews
* 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?
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 opencode@microsoft.com with any additional questions or comments.