uwsgi 上的应用程序和使用烧瓶的 OpenTelemetry 不会跟踪不同命名空间中的 API

Question

我们有一个使用 uwsgi 和烧瓶运行的 python 微服务。 我们已经使用 OpenTelemetry 工具启用了跟踪。 但是，我们发现除了 app.py(main) 文件中的路由外，其他命名空间中的路由都没有被跟踪。

用于跟踪的示例代码

APP = Flask(__name__)
FlaskInstrumentor().instrument_app(APP)
RequestsInstrumentor().instrument()
PymongoInstrumentor().instrument()

# set provider
tracer_provider = TracerProvider(
    resource=Resource.create({SERVICE_NAME: "test service"}))
trace.set_tracer_provider(tracer_provider)

jaeger_exporter = JaegerExporter(
    agent_host_name="localhost",
    agent_port=6831)
span_processor = BatchSpanProcessor(jaeger_exporter)
# To print the traces on the console
trace.get_tracer_provider().add_span_processor(BatchSpanProcessor(ConsoleSpanExporter()))
trace.get_tracer_provider().add_span_processor(span_processor)

API = Api(APP, version='1.0', title='API routes',
          description='routes')
API.add_namespace(ns_role_v2, path="/test")
API.add_namespace(ns_role_v3, path="/testv3")

uwsgi 配置：

[uwsgi]
# -------------
# Settings:
# key = value
# Comments >> #
# -------------

strict
uid = root
gid = root

# socket = [addr:port]
http-socket = 0.0.0.0:8080

listen = 128

# WSGI module and callable
# module = [wsgi_module_name]:[application_callable_name]
module = app:APP

# master = [master process (true of false)]
master = true

# processes = [number of processes]
enable-threads = true
# threads = [number of threads (per worker process)]
threads = 8

vacuum = true
single-interpreter = true
no-threads-wait = true
die-on-term = true

# Dynamic Worker Scaling (cheaper)
# set cheaper algorithm to use, if not set default will be used
cheaper-algo = spare
# minimum number of workers to keep at all times
cheaper = 8
# number of workers to spawn at startup
cheaper-initial = 16
# maximum number of workers that can be spawned
workers = 64
# how many workers should be spawned at a time
cheaper-step = 8

logdate = %%F %%T

py-autoreload = 0

buffer-size = 65535

need-app = true

mules = 10

spooler-processes=16
spooler-frequency=10

但是，对于使用 gunicorn 和 flask 的微服务，跟踪对于不同命名空间中的所有路由都可以正常工作。

我们在这里需要帮助。