Filtering & Dropping

Timber offers the ability to filter and drop logs. This is great for noisy, low value logs, such as health check logs that you otherwise do not need.

{% hint style="warning" %}
This feature is currently in beta and is being actively improved as we receive feedback.
{% endhint %}

Getting Started

{% hint style="warning" %}
Filtering within the Timber web app is not currently available, but it is available through our API. Because this is such a simple feature, the instruction below use the Timber API directly.
{% endhint %}

Lines 1 and 4 were dropped because they both contained the "hello world" substring.

FAQs

Will I be charged for filtered / dropped logs?

No. Logs are dropped before they are counted towards your billing.

Why do you recommend dropping logs at the source?

It is much more efficient and alleviates your app from having to send the logs at all. If possible, we recommend not sending the log at all. In some cases this is not possible, such as logs generated by a hosted platform, and this is a great use case for filtering on the Timber side.

Can I drop logs based the value of an attribute?

Not yet. Log filtering is currently in beta and the first version shipped with sub-string matching only. We plan to add more options around matching and filtering in the future.

Can I drop logs with regex?

Not yet. Log filtering is currently in beta and the first version shipped with sub-string matching only. We plan to add more options around matching and filtering in the future.