Elmah MVC alternatives and similar packages
Based on the "Logging" category.
Alternatively, view Elmah MVC alternatives based on common mentions on social networks and blogs.
-
Semantic Logging Application Block (SLAB)
DISCONTINUED. Supporting semantic/structured logging for .NET -
ExcelDna.Diagnostics.Serilog
Integrate Excel-DNA Diagnostic Logging with your Serilog logging pipeling within your Excel-DNA add-in -
NLog.Targets.Pushover
DISCONTINUED. 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. -
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
InfluxDB high-performance time series database

* 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 MVC or a related project?
README
ELMAH.MVC
For painless integration of ELMAH into ASP.NET MVC application.
What's changed in 2.0 version?
For details, please follow that blog post - ELMAH.MVC v.2.0 - Release Candidate
What's the goal?
With ELMAH.MVC you got nice and clear MVC style routing to ELMAH error page. ELMAH can be accessed by:
http://yourapp.com/elmah
By doing that, you can apply any authorization strategies or routes. In short, no more
http://yourapp.com/elmah.axd
That could be used for ASP.NET session hijacking with Google and ELMAH.
How to use in my application?
Easy. Install ELMAH by NuGet, in package console
Install-Package Elmah.MVC
For further ELMAH configuration please check the documentation.
Should I use HandleErrorAttribute?
If you tried to use ELMAH in ASP.NET MVC, you are probably implemented your own HandleErrorAttribute, as it's shown in this example. You no longer need to apply this custom code with Elmah.MVC. As soon you installed package, so can safely remove your HandleError attribute, since it's already included into package.
Will exceptions be logged in "customError='On'" mode?
Yes, even if you configured application to use custom error pages, the exception will be logged.
How can I configure Elmah.MVC?
There is a simple configuration section in web.config file.
<appSettings>
<add key="elmah.mvc.disableHandler" value="false" />
<add key="elmah.mvc.disableHandleErrorFilter" value="false" />
<add key="elmah.mvc.requiresAuthentication" value="false" />
<add key="elmah.mvc.IgnoreDefaultRoute" value="false" />
<add key="elmah.mvc.allowedRoles" value="*" />
<add key="elmah.mvc.allowedUsers" value="*" />
<add key="elmah.mvc.route" value="elmah" />
<add key="elmah.mvc.UserAuthCaseSensitive" value="true" />
</appSettings>
elmah.mvc.disableHandler
- turn on/off ELMAH.MVC handlerelmah.mvc.disableHandleErrorFilter
- by defaultHandleErrorAttribute()
is set as global filter, to disable it, set value to "true"elmah.mvc.requiresAuthentication
- secure /elmah route with authenticationelmah.mvc.allowedRoles
- in case of authentication is turned on, you can specify exact roles of user that have access (eg. "Admins")elmah.mvc.allowedUsers
- in case of authentication is turned on, you can specify exact users that have access (eg. "johndoe")elmah.mvc.route
- configure ELMAH.MVC access route
You can either disable handler or apply authentication, based on application roles.
You can also tweek the ELMAH default route. If you just install the package, ELMAH will be availabled at /elmah
, howether if you would like to change that, change elmah.mvc.route
, this setting is a MVC route prefix, used during ELMAH routes registration. For instance, if you change that to secure/admin/errors
you will get ELMAH at http://yourapp.com/secure/admin/errors
.
Default route issue
You might change the elmah.mvc.route
to a custom one, but still able to see ELMAH reports at /elmah
. This issue is caused by the way how ASP.NET MVC matches controllers in separate namespaces. There are no good workaround for that (at least one I know), so if I makes a trouble to you, I recommend to reconsider the application, without using default route.
UPDATE: You might also consider ignoring /elmah
route explicitly as described here.
UPDATE 2: @chaoaretasty has added an option, to allow ignoring default role. Set elmah.mvc.IgnoreDefaultRoute
setting option to true
.
Related articles and posts
ELMAH.MVC v.2.0.0 - Release Candidate
ELMAH MVC controller released on NuGet
Integrating ELMAH to ASP.NET MVC in right way
Recent changes
- 30-Apr-2015 - v.2.1.2 Added
UserAuthCaseSensitive
setting by @issafram.IgnoreDefaultRoute
now works for subfolders by @DavidDeSloovere. - 09-Jul-2013 - v.2.1.1 fixes by @papci
- 01-Jul-2013 - v.2.1.0 user based authentication by @papci
- 02-Jun-2013 - v.2.0.3 ignoring default role by @chaoaretasty
- 06-Nov-2012 - v.2.0.2 flag to turn on/off default HandleErrorAttribute()
- 16-Aug-2012 - v.2.0.1 custom routes, VB.NET support
- 13-Jun-2012 - v.2.0 major changes, packed to class library, HandleError attribute etc.
- 11-Jan-2012 - minor style changes and readme correction
- 29-Aug-2011 - nuget package created
- 29-Aug-2011 - reimplemented controller to avoid usage of additional routing instructions
Licence
*Note that all licence references and agreements mentioned in the Elmah MVC README section above
are relevant to that project's source code only.