Investigate support for FastAPI and FastAPI SQL Alchemy

Open
#600 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
fastapi, python, sqlalchemy
Domain
backend, databases, observability

Research direction

Start by reviewing the existing Starlette integration and reproducing a FastAPI application that uses the FastAPI SQL Alchemy library. Trace the request and SQL timing collection paths to determine why timings are aggregated under “View.” Done means SQL timings are collected separately and the relevant behavior is covered by a regression test.

Written by the indexing model from the issue text.

Description

From initial appearance, it looks like our Starlette integration works pretty well for FastAPI, but it doesn't appear that SQL timings are being collected when using the FastAPI SQL Alchemy library. Everything gets aggregated under 'View'

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.