Add an option similar to shouldCreateSpanForRequest to not create certain spans.

[rodolfoBee]

Problem Statement

Similar to this issue, Sentry's Django automatic instrumentation can create a large number of spans that can be irrelevant for users.

The options to control which operations create spans are limited, it is a simple on/off switch for middleware, signals and cache spans.

Solution Brainstorm

The JS SDK has an option to not create spans for certain urls, the solution can be same for spans matching a criteria (description, operation, specific signal)

[antonpirker]

Hey @rodolfoBee
Thanks for bringing this up. We have a traces_sampler (see https://docs.sentry.io/platforms/python/configuration/sampling/#setting-a-sampling-function) where users can specify a function that can decide what traces to keep and which ones to drop.

We could add something similar for spans. A function that gets the span as an argument and it can decide to keep or drop it.

[sentrivana]

Closing in favor of #3859