We’ve re-designed the Delete Log dialog to better communicate the impact of log removal. To prevent accidental deletions, you’re now required to type the log’s name to confirm, matching the workflow used by Azure and GitHub.
Support for using the Contains and Does not contain conditions has been extended to also cover the URL field when adding new filters to the search page. You can use this to find log messages that contain parts of a URL. Notice that you can also use wildcards, like in the following example that finds all URLs with a file extension of .php:
There’s a new recommendation created when the Lighthouse check is enabled on an uptime check, and the scores drop below a certain value. The Impact follows those of Lighthouse itself, where a score below 50 creates a High impact recommendation and a score between 50 and 89 creates a Medium impact recommendation.
There’s a new recommendation that is automatically created based on logs without any notifications configured. A notification either covers emails, HTTP rules, or app integrations. This can help you identify logs that are not actively monitored.
For logs where no notifications are accepted (like development logs), you can mark the recommendation as ignored.
A new email type has been added: New Recommendation. Enabling this email will send you an email when a new recommendation is created on a log or if a recommendation marked as fixed has been reopened. This way, you can monitor when the various elmah.io features add new recommendations.
The New Recommendation email can be enabled either when creating/editing a log from the dashboard (through the redesigned dialog) or on the Emails tab on your profile.
https://blog.elmah.io/pimplementing-strongly-typed-ids-in-net-for-safer-domain-models/
Stop using primitive types for IDs. Learn how to implement strongly-typed IDs in .NET and EF Core to catch logic errors at compile time.
The Add/Edit log control available from the dashboard has been redesigned. Instead of the flipping card effect, this feature is now presented as a slide-in. This makes the feature match other places where data is edited, while also creating more room for new content. One addition already made is the option to select whether the log should be included in the individual or combined daily digest emails. A new email type will be added soon, so stay tuned for updates.
Bugster can now help analyze failing uptime monitoring checks. As on other errors, you can click the Analyze with Bugster button on the error details. When analyzing uptime errors, Bugster automatically fetches results from the selected regions to help you determine why an endpoint fails and what you can do to resolve the issue.
https://blog.elmah.io/new-in-net-10-and-c-14-multi-tenant-rate-limiting/
Learn how to implement multi-tenant rate limiting in .NET 10 and C# 14. Master native partitioning to prevent noisy-neighbor issues in SaaS.
We have migrated the final suggestion log messages to recommendations. Messages from the SSL checks and ELMAH checks are now created as recommendations on the tab with the same name on the Log Search page. Like the previous recommendations, these messages are still created as both log messages and recommendations. Once we add new notification methods for recommendations, the log message creation will be removed.
We released a new version (4.2.0) of the Elmah.Io.JavaScript package. The new version includes the following changes:
There’s a new Timestamp Format setting on your profile. Using this dropdown, you can control how timestamps are formatted within the elmah.io UI. Relative is the default choice, corresponding to how the UI has been displayed in the past. But if you select Absolute, the full timestamp is shown instead.
Part of this change also means the removal of the Show full time toggle on the Columns configuration dialog. If you had this toggle enabled, you will need to go to your profile and select Absolute to get timestamps displayed in the same way on the log search page.
https://blog.elmah.io/new-in-net-10-and-c-14-fast-model-validation-for-apis/
Explore the performance gains in .NET 10 and C# 14. Compare model validation benchmarks and see how reflection-free metadata cuts latency by 3x.
We released a new version (5.3.58) of the Serilog.Sinks.ElmahIo package. The new version includes the following changes:
The new Recommendations feature, recently announced, has been updated with more recommendations. When enabling Security Header Check on an uptime check, any issues will now be saved as recommendations:
https://blog.elmah.io/new-in-net-10-and-c-14-enhancements-in-apis-request-response-pipeline/
Explore how .NET 10 and C# 14 boost API performance. Learn about static lambdas, JSON optimizations, and benchmarks that improve response times.
A new icon has been added to the Users list on the Organization Settings page, indicating when a user is part of the organization but does not have access. This can happen if you have set up custom security by clicking the Security button, and the user doesn’t meet those requirements.
Example: 2FA is required, but a user without 2FA configured on their account has been added to the organization:
You may have already noticed the new Recommendations tab on the log search page. Recommendations is a new concept on elmah.io that we silently launched some time ago. Recommendations are intended as a list of suggestions and best practices for your website, domain, and other relevant areas, identified through various elmah.io features. In the past, we have logged recommendations as log messages, which caused the messages to disappear among regular logging.
Recommendations are found on the log search page:
Suggestions already migrated to recommendations are:
We still log both a log message and a recommendation on these issues, but the plan is to move entirely to recommendations once the feature is fully rolled out.
In the future, new types of recommendations will be added. These could be suggestions for optimizing logging config in your clients, failing apps and integrations, changes in Lighthouse score, and more.
The error spike message logged as part of the machine learning/AI feature has been improved, utilizing the new markdown support in the details field. The description now shows up nicely formatted and containing permalinks to the error spikes:
https://blog.elmah.io/new-in-net-10-and-c-14-ef-core-10s-faster-production-queries/
Explore .NET 10 and C# 14’s impact on EF Core 10. Benchmarks reveal a 25-50% speed boost in data fetching through JIT and pipeline upgrades.