There’s a new optional Parent setting on the Azure Boards app. If you input a work item ID from your Azure DevOps project, elmah.io will automatically add that work item as a parent to any created bugs through the integration. You can use this to group issues created by elmah.io beneath another issue, an epic, or similar.
There’s a new (experimental) package named Elmah.Io.Functions.Isolated for isolated Azure Functions running on .NET 5. Much like the Elmah.Io.Functions package, this new package will log all uncaught exceptions happening inside functions and include contextual information (like HTTP headers) not included through Microsoft.Extensions.Logging-based logging. Learn how to get started in the updated documentation and check out the samples.
New prereleases have been published for all client integrations available on GitHub and NuGet. A lot of good stuff goes into the new version like extended documentation and better handling of AggregateException.
We have also started the work on improving the use of the embedded HttpClient within the client. The new versions will start marking the HttpClient property on IElmahioAPI and ElmahioAPI as obsolete. If you are currently using this property in your code, reach out to get help migrating.
As usual, we will write individual changelogs once each package is released as stable. For now, feel free to start playing with the new versions, but remember the prerelease tag 😉
We have improved the way the country is resolved on log messages. By looking at multiple headers and server variables we are able to resolve the country of the user causing an error in even more cases.
We released a new version (1.1.0) of the netStack.js library. That’s the jQuery plugin that nicely formats stack traces within the elmah.io app and the Stack Trace Formatter. The new version contains support for Russian stack traces and a bugfix. Let us know if it causes any problems.
If you need to format and syntax highlight .NET stack traces in your own software, take a look at netStack.js.
Values on the log message details view can now be easily copied with the new copy icon available when hovering each value:
Zaps created through the elmah.io integration with Zapier are now available on the Rules tab. This will make it easier to see which integrations are currently configured and webhooks can be deleted when no longer needed.
Log environments have been added in multiple locations on the organization overview to make it easier to understand log names:
Apps can now be enabled and disabled directly from the Apps page. This way, you no longer need to remove an app to temporarily disable it.
In some cases, we will start disabling misconfigured apps. When doing so, an error message will be shown on the app with instructions on what to fix before enabling the app.
There’s a new step template available in the Octopus Deploy Library for uploading source maps to elmah.io from Octopus Deploy.
In short, adding a step to your process will upload a minified JavaScript file and source map to elmah.io:
There’s a new section in the Source map documentation explaining this in more detail: https://docs.elmah.io/sourcemaps/#upload-from-octopus-deploy. Be aware that the server-side source map feature is still in beta.
We went through what I believe are the last integrations missing the Environment field. Information about the log environment has been added to:
We published a new issue of the elmah.io Newsletter: https://us7.campaign-archive.com/?u=66fdd2122e968863d381a26e1&id=251a3789a3
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
The filename of embedded source code is now shown within the elmah.io UI. Attaching a filename requires Elmah.Io.Client.Extensions.SourceCode version 4.0.19 or newer.
There’s a brand new extension available in the Azure DevOps Marketplace for uploading source maps to elmah.io from Azure DevOps Pipelines.
In short, adding a task to your pipeline will upload a minified JavaScript file and source map to elmah.io:
There’s a new section in the Source map documentation explaining this in more detail: https://docs.elmah.io/sourcemaps/#upload-from-azure-devops. Be aware that the server-side source map feature is still in beta.
We released a new version (4.0.19) of the Elmah.Io.Client.Extensions.SourceCode package. The new version includes the following changes:
useCacheIfPossible flag to control the internal cache.