Filters help you stay within your message limit
Since launching this feature, all of the integrations with elmah.io now have local filtering options. We recommend you filter unwanted log messages on your side to avoid you hitting API request limits, reducing outbound network traffic, etc. For instructions on how to create client-side filtering, look up the documentation for the integration you are using (Serilog, ASP.NET Core, NLog, etc.).
As we are getting ready to enforce message limits, we want to provide some additional tools to help you stay within your limit. The first one is simply named Filters.
Like apps are a nice UI on top of primarily HTTP rules, Filters are a new UI on top of Ignore rules. Unlike Ignore rules, where you have to create everything yourself, filters can be enabled/disabled by clicking a checkbox. In this first launch, we have analyzed currently logged messages and added three filters which should ignore a lot of errors, but still log all errors happening in your system.
Filters are available on the Log Settings view as shown here:
Enabling or disabling a filter requires nothing more than clicking the toggle. We hope that Filters will help you focus on the important errors.
We monitor your websites
We monitor your websites for crashes and availability. This helps you get an overview of the quality of your applications and to spot trends in your releases.
We notify you
We notify you when errors starts happening using Slack, Microsoft Teams, mail or other forms of communication to help you react to errors before your users do.
We help you fix bugs
We help you fix bugs quickly by combining error diagnostic information with innovative quick fixes and answers from Stack Overflow and social media.