Track Flask WSGI middleware

Open
#396 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
flask, python
Domain
backend, observability

Research direction

Start at Flask's wsgi_app entry point and compare how the Django integration tracks middleware. Determine the middleware information that should be recorded for a Flask app, then verify that Flask middleware is tracked consistently with the Django integration.

Written by the indexing model from the issue text.

Description

If a Flask app has WSGI middleware set it will be done so by wrapping its wsgi_app attribute. It might be worth tracking the middleware set here, just like the Django integration does.

Dominant language
Python
Stars
77
Forks
19
Avg merge
1d 9h
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scoutapp/scout_apm_python

All issues in scoutapp/scout_apm_python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.