Use canonical name for aiohttp request span name#3896
Conversation
1ba9a1c to
8689cfc
Compare
bisgaard-itis
left a comment
There was a problem hiding this comment.
Looks good. Thanks a lot for the effort! 👍🏻
c05f041 to
3bb8b84
Compare
Co-authored-by: Tammy Baylis <96076570+tammy-baylis-swi@users.noreply.github.com>
5f4116a to
32ccac9
Compare
tammy-baylis-swi
left a comment
There was a problem hiding this comment.
Thank you @krnr for this. Lgtm though I want some other Approvers to have a look at this change.
If you wanted to bring this up more synchronously, please feel welcome to join the Python SIG meeting on Zoom on Thursdays -- Calendar with links here. Else this PR should still be visible on the PR digest board.
…rc/opentelemetry/instrumentation/aiohttp_server/__init__.py Co-authored-by: Tammy Baylis <96076570+tammy-baylis-swi@users.noreply.github.com>
|
This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment. |
|
Hi @xrmx I've just resolved some conflicts. Any other suggestions? |
|
This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment. |
|
This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment. |
Description
Current implementation doesn't use canonical attribute of a
Resource, which leads to the situation when generated spans all have unique names. It creates high cardinality of spans. Other frameworks that use path params create spans with "canonical" paths in names (e.g. fastapi [1] )Type of change
How Has This Been Tested?
add a new unit test:
test_url_params_instrumentationDoes This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.