On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk internals and the time spent in the Authentication step when calling an Authentication server. The details of Tyk internals is not relevant for this population.

Solution : Find some way to be able to both keep the detailled spans of Tyk middlewares for Tyk's admin team when needing for its internal tracing dashboard, while allowing to get a trace with less spans for the tracing dashboard used by upstream API teams.

It may be the trigger of two distincts traces sent to two distincts trace repositories.

It may be a way to filter out some spans in the zipkin/jaeger dashboard.

Alternative : be able to configure the middlewares that we want to appear in the trace, globally for an organization, or per API Definition.