elmah.io changelog

There’s a brand new integration available in the GitHub Marketplace for uploading source maps to elmah.io from GitHub Actions.

In short, adding a build step to your YAML file will upload a minified JavaScript file and source map to elmah.io:

uses: elmahio/github-upload-source-map-action@v1
with:
  apiKey: $
  logId: $
  path: '/bundles/sharedbundle.min.js'
  sourceMap: 'path/to/sharedbundle.map'
  minifiedJavaScript: 'path/to/sharedbundle.min.js'

There’s a new section in the Source map documentation explaining this in more detail: https://docs.elmah.io/sourcemaps/#upload-from-github-actions. Be aware that the server-side source map feature is still in beta.

There’s a brand new integration available in the GitHub Marketplace for creating elmah.io deployments from GitHub Actions.

In short, adding a build step to your YAML file will notify elmah.io about a new deployment without you having to add any custom script:

- name: Create Deployment on elmah.io
  uses: elmahio/github-create-deployment-action@v1
  with:
    apiKey: $
    version: '1.0.0'

The documentation has been updated to reflect the new action.

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

• Fixed a bug that prevented the script from logging the errors when it was dynamically or async/defer loaded in IIFE mode.
• Made breadcrumbs options parameter optional in typescript mapping.
• Fixed a bug where adding breadcrumb manually could throw an error.
• Added two new React samples.

https://blog.elmah.io/logging-in-unity/

Server-side JavaScript source map support has been launched in beta. In case you don’t want to upload source maps alongside bundled and minified JavaScript files, you can integrate source map upload into your CI/CD pipeline or upload them manually through the elmah.io API. Check out the new source map documentation for details. Server-side source map support is currently in beta and not recommended for production use.

The JavaScript documentation has been re-structured to its own main menu item on docs.elmah.io, making room for more specific help articles: https://docs.elmah.io/logging-to-elmah-io-from-javascript/.

While moving around, we also updated the React documentation to reflect the recent changes happening in React and produced two new samples: elmahio-react and elmahio-react-typescript.

There’s a new toggle on the Slack app named New Errors. By disabling this toggle, you can create an integration with Slack that only notifies you about Uptime Monitoring issues or similar:

There’s a new set of predefined queries when creating new rules. This will make it easier to create new rules with commonly used queries like New Error or Fatal message. You can still input custom queries by choosing the Custom query option:

There’s a new version of the elmah.io extension for Visual Studio. The new version contains a range of bug fixes and some internal restructuring to support Visual Studio 2022. The Visual Studio Marketplace doesn’t yet support extensions with both 2019 and 2022 support in the same listing why we have uploaded a preview of the 2022 version here: https://marketplace.visualstudio.com/items?itemName=elmahio.elmahiobrowser2022. Feel free to play around with it if you are experimenting with Visual Studio 2022 (we are and we like what we have seen so far).

Microsoft no longer seems to support links in the headline in Teams messages, why we added a new View button in all messages. Clicking the View button will take you directly to the logged messages on elmah.io. To get the new app, please re-install the Microsoft Teams app on the log settings page.

Microsoft recently changed something around the webhook URLs generated by integrations like the one with elmah.io. If you are having trouble getting messages through to Teams, please check out this Troubleshooting document for help.

There’s a new Date option, grouping log messages by the logged day.

As already announced, there’s a new setting to switch between 12 and 24-hour time format on your profile. Today, there’s yet another advantage of choosing the correct format. Emails have been upgraded to support the selected format too:

https://blog.elmah.io/how-to-authorize-and-post-slack-messages-from-asp-net-core/

We started playing with a new feature that will bring source code into the elmah.io UI. The feature is not ready for production, but if anyone wants to play with it, there’s a help article here: How to include source code in log messages.

There’s a new setting on your profile that will let you change all dates on elmah.io from 12-hour to 24-hour format. All of the UI is updated and timestamps in emails will follow shortly.

We have published new prerelease versions of an upcoming major version bump of all integrations. The new integrations will all be version 4.* and up. The integrations depend on the new Elmah.Io.Client v4 package which is generated with NSwag instead of AutoRest. We have tried supporting most of the existing code from the v3 package, but some minor code changes may be needed after upgrading. Most upgrades shouldn’t cause any problem, but additional help is available right here: Upgrade elmah.io from v3 to v4.

As always, don’t run with prerelease packages in production. These versions are for preview only.

https://blog.elmah.io/upload-and-resize-an-image-natively-with-asp-net-core/

We released a new version (3.5.1) of the Elmah.Io.JavaScript package. The new version includes a bug fix on the Breadcrumbs feature introduced in 3.5.0.

https://blog.elmah.io/show-a-name-and-profile-photo-with-dotnet-and-gravatar/

If you don’t like the “x days ago” format on each log message row in the search result, you can switch to a more regular date format with the new toggle available in the Customize columns dialog: