FastAPI record api pattern as name not specific end_point

[BrikerMan]

Is your feature request related to a problem? Please describe.
I'm always frustrated when API grouped by API names, for example, this is my API.

from typing import Optional
from fastapi import FastAPI

app = FastAPI()

@app.get("/items/{item_id}")
def read_item(item_id: int, q: Optional[str] = None):
    return {"item_id": item_id, "q": q}

When I have API calls

• curl 127.0.0.1:8000/items/1
• curl 127.0.0.1:8000/items/2
• curl 127.0.0.1:8000/items/3
• curl 127.0.0.1:8000/items/4

Then it will show as 4 separate requests on the APM UI, rather than aggregated with the name GET /items/{item_id}.

Current result is

• GET 127.0.0.1:8000/items/1
• GET 127.0.0.1:8000/items/2
• GET 127.0.0.1:8000/items/3
• GET 127.0.0.1:8000/items/4

But it should be,

• GET 127.0.0.1:8000/items/{item_id}

Describe the solution you'd like
Use request pattern /items/{item_id} for the transition name, not the specific URL.

Additional context
When I use flask, the APM agent behaves in this way.

[BrikerMan]

Here is an example of how to access the API path in middle-ware, tiangolo/fastapi#486.

[BrikerMan]

Duplicated with #833, closed.