elmah.io changelog

The current message and email consumption counters are now available directly on the dashboard.

You can still get extended details on the Subscription tab on the organization settings page.

We have launched a new feature on elmah.io called Correlations. With Correlations, you can correlate/group log messages across multiple sites and services together. Think of a console app calling an API that puts a message on a queue that a service consumes. By correlating log messages from all three processes, you will be able to see a shared trace of what happens.

I won’t go into more detail here, since the feature is already described here: How to correlate messages across services. The Correlations feature is currently in beta and will in some cases require you to install prerelease NuGet packages. I look forward to hearing what you think.

We released a new version (3.5.6) of the Elmah.Io.Umbraco package. The new version includes the following changes:

• Build moved from AppVeyor to GitHub Actions.
• SourceLink support on NuGet package.
• Running on the newest versions of the Elmah.Io.Client, Elmah.Io, and Serilog.Sinks.ElmahIo packages.

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

• SourceLink support on NuGet package.
• Running on the newest version of the Elmah.Io.Client package.
• Using the new ToDataList method from the client that collects all exception properties recursively.
• New sample for ASP.NET Core 3.1.

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

• Build moved from AppVeyor to GitHub Actions.
• SourceLink support on NuGet package.
• Running on the newest version of the Elmah.Io.Client package.

New versions of the helper packages Elmah.Io.Mvc, Elmah.Io.WebApi, and Elmah.Io.AspNet have been released as well.

We released a new version (3.1.7) of the Elmah.Io.Heartbeats.Hangfire package. The new version includes the following changes:

• Build moved from AppVeyor to GitHub Actions.
• SourceLink support on NuGet package.
• Running on the newest version of the Elmah.Io.Client package.
• New sample for ASP.NET Core 3.1.

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

• Build moved from AppVeyor to GitHub Actions.
• SourceLink support on NuGet package.
• Running on the newest version of the Elmah.Io.Client package.

We released a new version (3.4.10) of the Elmah.Io.Functions package. The new version includes the following changes:

• Build moved from AppVeyor to GitHub Actions.
• SourceLink support on NuGet package.
• Running on the newest version of the Elmah.Io.Client package.
• Updated samples to Functions v3 runtime.
• Configurable timeout when communicating with the elmah.io API.
• Log function name in Data.

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

• Build moved from AppVeyor to GitHub Actions.
• SourceLink support on NuGet package.
• Running on the newest version of the Elmah.Io.Client package.

We made some large updates to elmah.io Uptime Monitoring like configurable regions and adding 4 more regions. Check out the following blog post for detailed information: Major updates to elmah.io Uptime Monitoring

We released a new version (3.8.11) of the Elmah.Io.NLog package. The new version includes the following changes:

• Build moved from AppVeyor to GitHub Actions.
• SourceLink support on NuGet package.
• Running on the newest version of the Elmah.Io.Client package.
• Include exception data dictionary in log message.
• Updated ASP.NET Core sample to 3.1.

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

• Build moved from AppVeyor to GitHub Actions.
• SourceLink support on NuGet package.
• Running on the newest version of the Elmah.Io.Client package.
• Updated samples for all LTS versions of ASP.NET Core plus a .NET 5 sample.
• Tag helper for Elmah.Io.JavaScript now references 3.3.1.

We released a new version (3.10.10) of the Elmah.Io.Client package. The new version includes the following changes:

• Build moved from AppVeyor to GitHub Actions.
• SourceLink support on NuGet package.
• CorrelationId property added to log messages. The correlation ID is something that we are currently working on implementing on the app.

https://blog.elmah.io/building-and-testing-on-multiple-net-versions-with-github-actions/

Four new columns found their way to the Customize columns modal:

• Severity
• Browser
• Country
• Version

https://blog.elmah.io/how-to-add-user-agent-header-to-httpclient-in-net/

There’s a new filter available for users with the Machine Learning feature named: Filter Bot Suggestions. As suggested by the name, the filter will automatically ignore warning, error, and fatal messages predicted to have been generated by a bot.

https://blog.elmah.io/predicting-die-hard-fans-with-ml-net-and-csharp/

There’s a new bot suggestion message shown on log messages suspected as generated by an automated bot/spider/crawler. The suggestion is being generated by machine learning and is available on plans with the Machine Learning feature.

You can mark the error group as generated by a bot or not directly from the message or you can hide the message once (by clicking the close icon) or permanently.

In the future, you will be able to execute actions based on the new flag. Like ignoring similar messages going forward.

There’s a new help article showing how to log to elmah.io from Google Cloud Functions:

https://docs.elmah.io/logging-to-elmah-io-from-google-cloud-functions/