Redesigns message grouping so similar errors collapse into a single control with an instance counter and navigation between occurrences, while every message stays individually stored rather than collapsed into a bare count, with smarter grouping and bulk actions planned next. ...
Shows how to stamp elmah.io messages with a version number via the client's OnMessage event and an appSettings key, then automates it on Kudu git deployments using a Web.config transform plus a PowerShell Post Deployment Action Hook that timestamps the release. ...
Reintroduces a single-user Startup plan at $9/month (soon rising to $19) aimed at founders, alongside a Small Business plan price bump from $19 to $29, with existing customers grandfathered onto their current pricing. ...
A hands-on guide to writing a custom ELMAH error logger by extending the ErrorLog class from the elmah.corelibrary NuGet package, implementing Log, GetError, and paginated GetErrors, and mapping errors to and from ErrorLogEntry. ...
Details new App Store manifest options beyond plain string key/value settings, adding numbers, choice dropdowns, and default values, showcased in a new Playground app, as elmah.io looks for community developers to build more of its 9 point-and-click apps. ...
Introduces a new Usage tab under your profile with a progress bar tracking logged messages against your plan's hard limit (e.g. 25,000/month on Business), plus warning and burst-through emails prompting a log clear-out or plan upgrade. ...
Announces the Logary.Targets.Elmah.Io NuGet package (not to be confused with the old Logary.Targets.ElmahIO) with a C# LogaryFactory example wiring a target to a log ID, bringing F#-friendly Logary logging to elmah.io. ...
Explains how the search page now encodes filters like severity:Error, sort order, and grouping directly into the URL query string, so a specific search becomes bookmarkable and shareable in emails or issue trackers instead of re-typed each visit. ...
Demystifies ELMAH access control: the allowRemoteAccess flag on /elmah.axd, locking it down with web.config authorization roles/users elements, and the elmah.mvc.requiresAuthentication and allowedRoles app settings needed when using the Elmah.MVC package. ...