elmah.io changelog

We usually don’t publish minor changes on this changelog, but I want to put a few words on a recent improvement to avoid any confusion. We’ve changed the icon for the organization overview from the eye to a chart to better illustrate what feature will trigger when clicking the icon. While doing so, we also switched the two icons around in the menu and on the dashboard to match what is there for log settings and search. So, in the future, when you need to access organization settings, click the first icon (gears). And when you need to access the organization overview, click the second icon (chart).

https://blog.elmah.io/deploy-access-restricted-azure-website-from-devops-pipelines/

There’s a new endpoint on the API that can be used to mark multiple log messages as fixed:

The new endpoint is available in the latest prerelease of the Elmah.Io.Client NuGet package, from an HTTP client, or manually from Swagger UI.

To help you detect when an API key is being suspended by the API request limit, we have added a warning directly to the list of API keys. The warning will show as a small icon next to the key on suspended keys:

As shown in the screenshot, all API keys can make 500 requests per minute and 3.600 requests per hour.

The GitHub integration has been extended to include more fields as well as a link back to the full error details on elmah.io. To get the new integration, edit and save any existing GitHub apps or set it up using a personal access token or a fine-grained token as explained in the documentation.

https://blog.elmah.io/creating-visual-studio-extensions-using-roslyn-analyzers/

https://blog.elmah.io/creating-and-downloading-zip-files-with-asp-net-core/

There’s a new field on all log messages named Category. This may sound like a minor addition but it’s actually something that is available throughout a larger part of elmah.io. The category field can be set on all log messages stored through the API. The field and value show up inside the elmah.io UI on the details:

Unless you are logging messages manually through the API or the Elmah.Io.Client package, you typically don’t need to set the field. New prereleases have been published of the Elmah.Io.Extensions.Logging, Elmah.Io.NLog, Elmah.Io.Log4Net, and Serilog.Sinks.ElmahIo NuGet packages. These integrations automatically pick up the category from the logging framework and set the new field. Having a category or logger name is something common for all logging frameworks. We have adopted the name from Microsoft.Extensions.Logging which calls it Category, NLog and log4net call it LoggerName, and Serilog calls it SourceContext.

Besides being available as a field on the log message details, Category can be used from the search field, search filters, the group by dropdown, as a column on the search result, and as part of rules.

There’s a new integration in the elmah.io App Store: PagerDuty. PagerDuty is an incident platform supporting various integrations and notification methods like phone calls, SMS/text messages, and emails. With a few mouse clicks, setting up advanced notification rules for your team is easier than ever.

Check out the PagerDuty documentation for details on how to set it up.

We released a new version (4.2.21) of the Elmah.Io.UmbracoNuGet package. Unless serious security issues are found, new features will be added to the v5 package only (supporting Umbraco 10 and newer). The new version includes the following changes:

• Running on the newest versions of the Elmah.Io, Elmah.Io.Client, and Serilog.Sinks.ElmahIo NuGet packages.
• Build script modernization and package validation.

We released a new version (4.3.40) of the Elmah.Io, Elmah.Io.Mvc, Elmah.Io.WebApi, and Elmah.Io.AspNet NuGet packages. The new version includes the following changes:

• Upgraded sample to .NET 4.8.
• Running on the newest version of Elmah.Io.Client.
• Build script modernization and package validation.
• Added documentation on the ErrorLog class.

The Canonical Check feature is now out of beta. When enabling canonical checks on an endpoint, the following checks are automatically run daily:

• Check that HTTP redirects to HTTPS.
• Check that www redirects to non-www or non-www redirects to www.
• Check unnecessary redirect chains.
• Check the use of correct redirect status code.
• Check canonical URL metadata.
• Check any use of meta refresh metadata.

Canonical checks are available for all Enterprise customers.

We released a new version (4.2.22) of the Elmah.Io.Log4Net NuGet package. The new version includes the following changes:

• Added new samples for ASP.NET Core 7 and console application on .NET 7.
• Build script modernization, build on .NET 7, and package validation.
• Running on the newest version of Elmah.Io.Client.

We released a new version (4.2.25) of the Serilog.Sinks.ElmahIo NuGet package. The new version includes the following changes:

• Build script modernization, build on .NET 7, and package validation.
• Running on the newest version of Elmah.Io.Client.
• Upgraded ASP.NET Core sample to .NET 6.
• New sample for console application on .NET 7.

We released a new version (4.2.36) of the Elmah.Io.Extensions.Logging NuGet package. The new version includes the following changes:

• New Synchronous option to disable async logging (don’t do this if async logging works).
• Upgraded Microsoft.Extensions.Logging to 3.1.x (.NET Core older than 3.1 may still be supported but it’s not something we are testing anymore).
• Added documentation on all public methods and classes.
• Build script modernization, build on .NET 7, and package validation.
• Upgraded Azure Functions sample to functions runtime v4 on .NET 6.
• Added new samples for ASP.NET Core 7 and console application on .NET 7.
• Running on the newest version of Elmah.Io.Client.

We released a new version (4.3.38) of the Elmah.Io.AspNetCore NuGet package. The new version includes the following changes:

• Updated healthchecks sample to .NET 6.
• New ASP.NET Core 7 sample.
• Fixed a bug to avoid an exception being logged when the website restarts.
• Updated tag helper to install elmah.io.javascript version 3.7.1.
• Build script modernization, build on .NET 7, and package validation.
• Running on the newest version of Elmah.Io.Client.

There’s a new integration with PoShLog. For those of you who may not know PoShLog, it’s a PowerShell logging module built on top of Serilog. The elmah.io sink for PoShLog brings easy logging to elmah.io from PowerShell using code like this:

Import-Module PoShLog
Import-Module PoShLog.Sinks.ElmahIo

New-Logger |
    Add-SinkElmahIo -ApiKey 'API_KEY' -LogId 'LOG_ID' |
    Start-Logger

Write-ErrorLog 'Say My Name'

The integration is available in the PowerShell Gallery and documented on Logging to elmah.io from PowerShell.

We published a new issue of the elmah.io Newsletter: https://mailchi.mp/elmah/best-chrome-extensions-for-web-developers-and-more-elmah-io-news

If you want to receive an email every 2-3 months with all of the recent goodies on elmah.io, make sure to subscribe here: http://eepurl.com/dE1hCn

https://blog.elmah.io/logging-and-global-error-handling-in-net-7-wpf-applications/

You asked for it. We deliver 😊 There’s a new prerelease of support for Windows Presentation Foundation (WPF). The integration is implemented in the Elmah.Io.Wpf NuGet package. When installed, simply call the Init method to have uncaught exceptions logged in elmah.io:

ElmahIoWpf.Init(new ElmahIoWpfOptions
{
    ApiKey = "API_KEY",
    LogId = new Guid("LOG_ID")
});

The package already has some nice features like maintaining breadcrumbs, storing WPF properties, and more. To learn more, visit the updated documentation and check out the samples for both .NET Framework and .NET 6.