You may remember the (rather unhandy) dropdown to manage log access on a user on the organization settings page. This has been replaced with a slide-in to make it more consistent with the rest of the elmah.io UI. As part of the move, we also added environments to the list of logs to better support multiple logs with the same name in different environments:
The elmah.io API uses the Problem Details (rfc7807) specification to communicate errors back to the client. In a recent change, communication from the request limit feature has been changed to use Problem Details responses too, to avoid returning errors in different formats. The response status code still equals 429 and no changes are needed on your part unless you are inspecting the response body from request limit error responses. The new response looks like this:
1 request per hour is from a test environment. The production API accepts 500 requests per API key per minute and 3,600 requests per API key per hour.
We have improved the way CORS is implemented on the API. This doesn’t require changes on your part. I still want to mention it, in case it causes issues somewhere since the headers have been changed.
Previously, we were running on a hand-crafted CORS solution on the API that has now been migrated to the built-in CORS feature in ASP.NET Core. The old solution where returning un-needed response headers in all requests and there was a CORS problem when returning a response with an API request limit. Both issues have been fixed by moving to the built-in CORS feature. Let us know in the chat if you experience any problems.
You probably tried looking at a stack trace, locating the details about the failing file and line number, and then opening the source code in your favorite IDE to inspect what is going on in that file and line. A tedious process that requires you to clone the code, maybe check out a specific tag, launch Visual Studio or similar, and locate the file and line number. With the new Embedded source code feature, elmah.io make it possible to embed the failing line and the lines around it directly in the error. Check out the details in this introduction blog post: Embedding source code on errors logged to elmah.io.
Logs that are added to an environment now show the environment name in the (individual) Daily Digest email:
There’s a new toggle on the Microsoft Teams app named New Errors. By disabling this toggle, you can create an integration with Teams that only notifies you about Uptime Monitoring issues or similar:
We released a new version (4.0.8) of the Elmah.Io.Umbraco package. The new version includes the following change:
Elmah.Io.Client v4 package moving from AutoRest to NSwag.Upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We released a new version (4.0.13) of the Elmah.Io.Heartbeats.Hangfire package. The new version includes the following change:
Elmah.Io.Client v4 package moving from AutoRest to NSwag.Upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We released a new version (4.0.24) of the Elmah.Io.Extensions.Logging package. The new version includes the following change:
Elmah.Io.Client v4 package moving from AutoRest to NSwag.Upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We released a new version (4.0.30) of the Elmah.Io.AspNetCore package. The new version includes the following change:
Elmah.Io.Client v4 package moving from AutoRest to NSwag.elmah.io.javascript updated to 3.5.2.Upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We released a new version (4.0.2) of the Serilog.Sinks.ElmahIo package. The new version includes the following change:
Elmah.Io.Client v4 package moving from AutoRest to NSwag.Upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We released a new version (4.0.21) of the Elmah.Io.NLog package. The new version includes the following change:
Elmah.Io.Client v4 package moving from AutoRest to NSwag.Upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We released a new version (4.0.13) of the Elmah.Io.Log4Net package. The new version includes the following change:
Elmah.Io.Client v4 package moving from AutoRest to NSwag.Upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We released a new version (4.0.17) of the Elmah.Io.Functions package. The new version includes the following changes:
Elmah.Io.Client v4 package moving from AutoRest to NSwag.Took property (available on the heartbeat history view on elmah.io).Upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We released a new version (4.0.49) of the elmah.io CLI. The new version includes the following changes:
Elmah.Io.Client v4.Spectre.Console.We released a new version (4.0.25) of the Elmah.Io package. The release is built on top of the newest version of the new Elmah.Io.Client v4 package moving from AutoRest to NSwag.
Upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We released a new version (4.0.29) of the Elmah.Io.Client package. The new version includes the following changes:
4.0.29 is the foundation for the new series of 4.x packages. New releases of the client integrations like Elmah.Io.AspNetCore, Serilog.Sinks.ElmahIo, etc. will be released within the next days/weeks. If you are using a v3 integration, upgrading the Elmah.Io.Client to v4 won’t work until a 4.x version of your integration has been released. Also, upgrading from 3.x to 4.x may require changes in your code. Check out Upgrade elmah.io from v3 to v4 for details.
We have made three minor changes to the extended log message view:
