Uh oh!
There was an error while loading. Please reload this page.
feat: Add http.route attribute to http.server spans with parameterized routes - #22534
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
85949f1 to
ae9c5faCompareThere was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ae9c5fa. Configure here.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.

Adds the
http.routeattribute that was missing on a fewhttp.serverspans when we found a parameterized route. Mostly this concernedhttp.serverspans we emit manually from frameworks (as opposed to Node http integration) or spans we enhance from OTel-based framework telemetry (Next/Sveltekit).I decided against also adding
url.template, since this attribute is more used on the client-side. Will open a PR in conventions to disambiguate these attributes.For the node:http spans, we already set the attribute in the higher level integrations (express, koa, etc), so there was nothing to add there.
closes#22417