We released a new version (5.1.22) of the Elmah.Io.AspNetCore.Serilog package. The new version includes the following changes:
Serilog.Sinks.ElmahIo.Microsoft.SourceLink.GitHub to 8.0.0.There’s a new experimental integration for logging from WinUI to elmah.io. The integration can be added through NuGet:
dotnet add package Elmah.Io.WinUI --prerelease
And set up using a single line of code:
ElmahIoWinUI.Init(new ElmahIoWinUIOptions("API_KEY", new Guid("LOG_ID")));
All uncaught errors are now logged to elmah.io:
Full documentation available here: Logging to elmah.io from WinUI
As you may know, we have developed a range of free online tools we use internally to develop elmah.io. Most of our time is spent in Visual Studio + Code but sometimes it’s easier and more convenient to use online tools for common tasks like formatting things.
Recently, we released a new YAML formatter and validator that offers a couple of features that we either didn’t find anywhere else or at least didn’t have in the same tool.
We released a new version (5.1.43) of the Serilog.Sinks.ElmahIo package. The new version includes the following changes:
Elmah.Io.Client.Microsoft.SourceLink.GitHub to 8.0.0.We released a new version (5.1.34) of the Elmah.Io.Log4Net package. The new version includes the following changes:
Elmah.Io.AspNetCore.Log4Net to define framework reference to Microsoft.AspNetCore.App instead of package reference to Microsoft.AspNetCore.Http.Microsoft.SourceLink.GitHub to 8.0.0.Elmah.Io.Client.log4net to 2.0.15 (you can use a newer version if you prefer).We released a new version (5.2.49) of the Elmah.Io.NLog package. The new version includes the following changes:
ToDataList.NLog to 5.0.5 (you can use a newer version if you prefer).Microsoft.SourceLink.GitHub to 8.0.0.Elmah.Io.Client.We released a new version (5.1.76) of the Elmah.Io.Client package. The new version includes the following change:
Breadcrumb class would throw away the values.New minor versions of Elmah.Io.AspNetCore, Elmah.Io.Extensions.Logging, Elmah.Io.Client.Extensions.SourceCode, and Elmah.Io.Client.Extensions.Correlation will be released soon but won’t receive individual changelogs since the only change is updating the dependency version.
We released a new version (5.1.45) of the Elmah.Io.Client.Extensions.SourceCode package. The new version includes the following changes:
Elmah.Io.Client.Microsoft.SourceLink.GitHub to 8.0.0.We released a new version (5.1.11) of the Elmah.Io.Client.Extensions.Correlation package. The new version includes the following changes:
Elmah.Io.Client.Microsoft.SourceLink.GitHub to 8.0.0.We released a new version (5.1.52) of the Elmah.Io.Extensions.Logging package. The new version includes the following changes:
Microsoft.AspNetCore.App instead of installing ASP.NET Core NuGet packages. This only applies when using the Elmah.Io.AspNetCore.ExtensionsLogging package. When targeting .NET 8 we also install the Microsoft.Extensions.Logging in version 8.0.0.Elmah.Io.Client.Microsoft.SourceLink.GitHub to 8.0.0.We released a new version (5.1.65) of the Elmah.Io.AspNetCore package. The new version includes the following changes:
ElmahIoExceptionHandler class has been added. This implements the new IExceptionHandler interface introduced in .NET 8.Microsoft.AspNetCore.App instead of installing ASP.NET Core NuGet packages.Elmah.Io.JavaScript version 4.1.0.Elmah.Io.Client.Microsoft.SourceLink.GitHub to 8.0.0.We released a new version (5.1.75) of the Elmah.Io.Client package. The new version includes the following changes:
searchAfter parameter added to the GetAll and GetAllAsync methods when searching for log messages. The searchAfter parameter can be used as an alternative to pageIndex to fetch more than 10,000 log messages from a log. For details about the searchAfter parameter, you can read through this article: https://docs.elmah.io/using-the-rest-api/#searching-messages.Color, EnvironmentName, and Disabled properties on the CreateLog class. This will allow you to set these properties from C# rather than having to set them through the UI.Checks to heartbeats. With this change, you can split up a heartbeat into multiple checks with individual statuses. Checks will show up in the elmah.io UI when available on the heartbeat. Our client integrations that automatically store heartbeats will automatically start using checks when new versions are released. For details about Checks, you can read through this article: https://docs.elmah.io/setup-heartbeats/#checks.Newtonsoft.Json to 13.0.3 when targeting .NET 8 or newer. No matter what version of .NET you are targeting, we recommend installing version 13.0.3 manually to avoid known vulnerabilities in version 10.Microsoft.SourceLink.GitHub to 8.0.0.Unless you are using the Elmah.Io.Client package directly, there is no need to upgrade manually since the upcoming client integration versions will all install this package version.
We’ve open-sourced a GitHub Action that is rolling out to all of our client integrations built on GitHub. The Action runs through a repository, lists the usage of vulnerable NuGet packages, and fails the build if any vulnerabilities are found. The Action is available in the GitHub Marketplace.
There’s a new option for Enterprise users of the ChatGPT app: Azure-hosted models. With a model hosted on Azure (that’s where elmah.io is hosted) the input you provide when requesting AI assistance will never leave our data center. Using this approach, an OpenAI API key is not needed either.
(The ChatGPT is still in beta)
There’s a new help article showing how to create elmah.io deployments from GitLab Pipelines: https://docs.elmah.io/create-deployments-from-gitlab-pipelines/
The AFFECTED USERS view in both the organization and log overview is already known by those of you logging emails as part of the user field on log messages. For others, this will now show up as a brand new view in the organization pages.
We have extended the backend to also include log messages with user info, not an email for this view. This will make the view show up in scenarios where the user is something like an identifier from a database or a username. In logs that contain messages with both emails and identifiers stored in the same log, the view will highlight problematic users better. Previously, a user with an email could show up as the most affected user, while another user with an identifier and many more log messages would not show up at all.
