Allow customizing health check patterns

[amitnavindgi]

Problem Statement

It looks like the current set of glob patterns for a transaction to be considered a health check may not be comprehensive. Most that I know have the pattern */health* - for example, /health/status.

I understand that having custom ones for every Sentry customer may not be ideal. Especially for Sentry's customers in health care (irony?).

I'd love to see a feature that allows us to configure that list of patterns at an organization level.

Solution Brainstorm

The list is probably hard-coded somewhere. Make it configurable for each organization and front load it when accepting transactions from projects in that org.

Product Area

Settings - General

[getsantry[bot]]

Assigning to @getsentry/support for routing ⏲️

[getsantry[bot]]

Routing to @getsentry/product-owners-performance for triage ⏲️

[k-fish]

That's a great suggestion @amitnavindgi I'm going to forward this to the involved teams.

In the meantime if you need to exclude specific transactions beyond that list you can always add to ignoreTransactions on the sdk (which eg. uses this health check ignore list by default).

[getsantry[bot]]

Routing to @getsentry/product-owners-issues for triage ⏲️

[amitnavindgi]

Looks like ignore_transactions is not available in the Python SDK? I guess I can always just use before_send_transaction.