opentelemetry-python-contrib
opentelemetry-python-contrib copied to clipboard
Doc holes in FastAPI instrumentation
trafficstars
Mentioning FastAPI specifically as that's what I'm using but I wouldn't be surprised if it held true for the others. So coming to add opentelemetry instrumentation as someone primarily not using python but using other language ecosystems I don't want to rely on assumptions on what's provided as not every language is equally fleshed out in opentelemetry IME.
So in these docs https://opentelemetry-python-contrib.readthedocs.io/en/latest/instrumentation/fastapi/fastapi.html#usage the missing information for me is:
- What environment variables can set things up? Do I have ones like
OTEL_EXPORTER_OTLP_ENDPOINTOTEL_EXPORTER_OLTP_PROTOCOLOTEL_SERVICE_NAMEor does this have to be setup separately - Does trace propagation work or do I need manual intervention
- If it does work does it also work for websocket requests?
- How do I integrate logs so they show up as events
- There should be a link to the opentelemetry-instrumentation package I had to search pypi for it because it's not a very google friendly name (a lot of things related to general python, languages I use more often and opentelemetry in general)
- there should probably be an entry in the menu since opentelemetry-instrument is a contrib package
Hi @xrmx, is this issue still available to work on? If so, I’d be happy to contribute.