Skip to main content

Why isn't the Health Check inbound filter filtering some of my health check transactions?

Updated over a month ago

Issue

I've noticed that we have the Health Check inbound filter enabled, but we're still capturing health check transactions. Why aren't these transactions being filtered?

Applies To

  • Users capturing health check transactions

  • Users with the Health Check inbound filter enabled

Resolution

The Health Check inbound filter matches on specific glob patterns listed in our docs. If the transaction name (e.g. ping_health) doesn’t match any of those patterns, it won’t be filtered out by the inbound filter.

To drop these unmatched transactions, you’ll need to filter them on the client side using the SDK’s beforeSendTransaction callback option.

Did this answer your question?