There’s now an elmah.io Brand Guide available. In case you want to showcase your use of elmah.io, need our logo for internal documentation, or something third, please read through this guide. The guide also provides a downloadable icon pack with our logo in various formats and colors.
We published a new issue of the elmah.io Newsletter: https://mailchi.mp/elmah/mocking-httpclient-requests-for-csharp-unit-tests-15645787
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 Root Cause tab previously shown in the extended error details, has been moved to the error details shown when extending an error on the Search page. While moving the content, we also took the chance to give it an overhaul, making the information more available and consistent with the new Heartbeat view released last month:
Admittedly a few years overdue. But you can now delete your account directly from the elmah.io UI. As always, user accounts are automatically deleted when not part of an organization and inactive for a longer period. This new change introduces an Actions tab on your profile to manually delete your account:
Documentation has been added explaining the requirements needed to successfully delete an account.
Contains and does not contain filters have been heavily improved. Previously, these filter types only worked on terms, meaning that it was possible to search for whole words within a larger search string only. With the recent change, searching using contains and does not contain uses wildcards for a better search experience:
There’s a new Root Cause view available on missing and unhealthy heartbeat errors. The view combines the overall status and reason for a heartbeat either failing or missing. In addition, any bundled checks included as part of the heartbeat are shown on the right side of the view. Heartbeat Checks are a new feature already introduced on the API and currently in prerelease in the Elmah.Io.Client NuGet package. We also provide prerelease versions of the Elmah.Io.AspNetCore.HealthChecks and Elmah.Io.Umbraco packages that automatically fill in checks.
The documentation of including checks in Heartbeats will be written before the packages are moved to stable.
If you are showing one of elmah.io’s dashboards on an external monitor or want to do so, there are some improvements for you. Enabling a custom range, kiosk mode, and auto-refresh on all dashboards now updates the URL with these selected changes. This way, you can build the URL locally and copy it directly to the device outputting the content on the external screen. We also improved the dashboards by not showing the cookie popup, Intercom chat widget, etc. when kiosk mode is enabled.
In addition, there’s a new help article to get you started: How to show elmah.io dashboards on a big screen.
We just love seeing elmah.io put in action in your office. Feel free to send us a picture where you use elmah.io to monitor your systems. We have a nice collection by now 😊
The reason logged as part of both healthy and unhealthy heartbeats can now be seen directly on the History/timeline by clicking the info icon next to the status:
There’s a new help article explaining how to log heartbeats to elmah.io from Coravel scheduled tasks: Logging heartbeats from Coravel
We’ve had a few questions about elmah.io and .NET 8 so I’ll post a quick update here. All of our client integrations support .NET 8 in the recent stable versions. There are new prereleases of all integrations and most of them contain a .NET 8 sample (like the one for Elmah.Io.AspNetCore here).
The new prerelease of Elmah.Io.Client for .NET 8 requires Newtonsoft.Json version 13.0.3 so make sure to update that package. Once NSwag (the library we use to generate the client) moves to System.Text.Json we will move the client over as well. This will be done in a new major version since there may be breaking changes.
The cookie popup, that you have probably already interacted with on elmah.io, can now show up on app.elmah.io as well. If you have accepted cookies on elmah.io, you should not see the popup again on app.elmah.io.
The new popup introduces a better grouping of cookies and improved options for disabling different cookies. If you want to include the Intercom support widget (the message icon in the lower right corner) you will need to accept cookies of type Preferences. The Statistics group contains only Google Analytics and we don’t use any marketing cookies like Google Ads tracking, remarketing, or similar.
By navigating to the Details tab in the cookie popup, you can see a complete list of cookies used across the websites:
There’s a new help article explaining how to customize logging, through ILogger, to elmah.io when making requests using a HttpClient: Logging to elmah.io from HttpClient
We’ve noticed an increasing number of email addresses registered on elmah.io bouncing. Because we are charged with sending bounced emails, starting January 2024, bounced emails will be included in the monthly email quota.
Make sure to check if your email is causing a bounce on the profile:
We released a new version (5.1.83) of the elmah.io CLI. It has been a while since we last announced a new version of this tool so let’s summarize the changes since the last changelog:
UseRouting with MapControllerRoute.UseElmahIo call after UseRouting in Elmah.Io.AspNetCore.verbose switch.Elmah.Io.Extensions.Logging also checks correctly using to make sure that the right AddElmahIo method is called and not the one from Elmah.Io.AspNetCore.searchAfter parameter which will allow for exporting more than 10k messages.Elmah.Io.Client.Newtonsoft.Json to v13.Let’s celebrate the release with a screenshot of the diagnose in action with new hints included:
We see more and more people 👯 using emojis in log names (and even error messages 😮). To better support this we went through our entire message-handling pipeline and made some changes. Integrations ⚙️, emails 📧, and the UI 🗔 now fully support emojis so let your inner emoji freak loose 🙈😅🎉
