ELMAH alternatives and similar packages
Based on the "Logging" category.
Alternatively, view ELMAH alternatives based on common mentions on social networks and blogs.
NLog9.4 6.1 L2 ELMAH VS NLogNLog - Advanced and Structured Logging for Various .NET Platforms
Serilog9.2 7.2 L4 ELMAH VS SerilogSimple .NET logging with fully-structured events
Log4Net6.4 7.6 ELMAH VS Log4NetMirror of This is the Apache log4net logging project git repository.
StackExchange.Exceptional6.2 0.0 L3 ELMAH VS StackExchange.ExceptionalError handler used for the Stack Exchange network
Sentry5.6 8.6 ELMAH VS SentrySentry SDK for .NET
Logary5.0 0.0 ELMAH VS LogaryLogs and metrics are one! Professional logging, metrics and analytics for your apps.
Semantic Logging Application Block (SLAB)Supporting semantic/structured logging for .NET
Elmah MVC4.1 0.0 L4 ELMAH VS Elmah MVCPainless integration of ELMAH into ASP.NET MVC application
ZeroLog4.0 3.2 ELMAH VS ZeroLogA high-performance, zero-allocation .NET logging library.
NReco.Logging.File3.6 4.3 ELMAH VS NReco.Logging.FileGeneric file logger for .NET Core (FileLoggerProvider) with minimal dependencies
Rollbar.NET3.3 0.0 ELMAH VS Rollbar.NETRollbar for .NET
Sejil2.9 0.0 ELMAH VS SejilCapture, view and filter your ASP.net core log events right from your app
Tracer2.8 0.0 ELMAH VS TracerTracing rewriter using Fody
ULogViewer2.7 0.0 ELMAH VS ULogViewerCross-Platform Universal Log Viewer.
Logazmic2.2 0.0 L4 ELMAH VS LogazmicWindows log viewer for log4j
elmah.io1.9 4.5 L4 ELMAH VS elmah.ioELMAH error logger for sending errors to elmah.io.
Serilog.Sinks.Notepad1.9 0.0 ELMAH VS Serilog.Sinks.NotepadA Serilog sink that writes log events to Notepad as text or JSON
NPushOver1.7 0.0 L4 ELMAH VS NPushOverFull fledged, async, .Net Pushover client
BugGuardian1.5 0.0 ELMAH VS BugGuardianBugGuardian: Easily track you exceptions on Azure DevOps and TFS
Serilog.Sinks.ExcelDnaLogDisplayA Serilog sink that writes events to Excel-DNA LogDisplay
ExcelDna.Diagnostics.SerilogIntegrate Excel-DNA Diagnostic Logging with your Serilog logging pipeling within your Excel-DNA add-in
NLog.Targets.Pushover0.9 0.0 L5 ELMAH VS NLog.Targets.PushoverNLog.Targets.Pushover is a custom target for NLog enabling you to send logging messages to the Pushover service
FastLog.Net0.7 10.0 ELMAH VS FastLog.Net💯 High performance logger for .NET
Ac682.Extensions.Logging.Consolea provider for Microsoft.Extensions.Logging which provides a colored console logger.
BugSnagLogs errors. Includes useful diagnostic info like stack trace, session, release, etc. Has a free tier. [Free for OSS][$]
LoupeCentralized .NET logging and monitoring
Essential DiagnosticsExtends the inbuilt features of System.Diagnostics namespace to provide flexible logging
ONLYOFFICE Docs — document collaboration in your environment
* 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 ELMAH or a related project?
Please read this document carefully before using this release of ELMAH as it contains important information.
For peer help and support, vists the ELMAH Discussion Group. Report bugs and issues to the issue tracker on the project site. Avoid using the issue tracker to seek help with problems you are experiencing in installing or running ELMAH. That is what the discussion group is for.
The best way to get started with ELMAH is to take it for a spin by launching the supplied demo Web site. Simply go the root of your ELMAH distribution and execute the demo.cmd script. The demo Web site requires Microsoft .NET Framework 2.0.
Version 1.0 BETA 3 Notes
Upgrading from ELMAH 1.0 BETA 2(a)
Microsoft SQL Server Error Log
If you are using the Microsoft SQL Server (2000 or later) for your
error log then you should re-create the stored procedures found in the
supplied SQL script (see SQLServer.sql). The script does not contain
ALTER statements so you will have to drop the stored
procedures manually before applying the
CREATE PROCEDURE parts of the
script. Other than that, there have been no changes to the schema
since BETA 2a so existing data in your logs can be left as it is.
Oracle Error Log
The Oracle error log is new in BETA 3, but if you have been compiling
ELMAH from sources between BETA 2 and 3 and using Oracle for your
error log then you should re-create the
ELMAH$Error table, its
indicies and related packages using the supplied SQL script (see
Oracle.sql in your distribution). The script does not contain any
statements so you will have to drop the table and package manually
before applying the script. If you wish to preserve the logged error
data, you should consider archiving it in a backup. Please read the
comments in this script file carefully for hints on users and
synonyms. NB The original package has now been split in two to aid in
securing the database in enterprise scenarios.
VistaDB Error Log
The VistaDB error log is new in BETA 3, but if you have been compiling ELMAH from sources between BETA 2 and 3 and using VistaDB for your error log then you should delete the .vdb3 file and allow it to be re-created.
Microsoft Access Error Log
The Access error log is new in BETA 3, but if you have been compiling ELMAH from sources between BETA 2 and 3 and using Access for your error log then you should delete the .mdb file and allow it to be re-created.
Version 1.0 BETA 2(a) Notes
Upgrading from GDN-ELMAH or ELMAH 1.0 BETA 1
The configuration sections and entries have changed slightly if you
are using GDN-ELMAH, which is the original that was released on
GotDotNet. Consult the
samples/web.config file to see examples of how
the configuration looks like now.
If you are using the Microsoft SQL Server for your error log then you
should re-create the
ELMAH_Error table, its indicies and related
stored procedures using the supplied SQL script (see
your distribution). The script does not contain DDL
DROP statements so
you will have to drop the table and stored procedures manually before
applying the script. If you wish to preserve the logged error data,
you should consider archiving it in a backup.
$Revision: 511 $