Filters help you stay within your message limit

Since launching this feature, all of the integrations with 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. Error logging and Uptime Monitoring for your web apps

This blog post is brought to you by is error logging, uptime monitoring, deployment tracking, and service heartbeats for your .NET and JavaScript applications. Stop relying on your users to notify you when something is wrong or dig through hundreds of megabytes of log files spread across servers. With, we store all of your log messages, notify you through popular channels like email, Slack, and Microsoft Teams, and help you fix errors fast.

See how we can help you monitor your website for crashes Monitor your website