-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ref: Remove usage of span tags #10808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
size-limit report 📦
|
060bcf8
to
83b1506
Compare
dev-packages/node-integration-tests/suites/tracing-experimental/nestjs/scenario.ts
Outdated
Show resolved
Hide resolved
83b1506
to
077a19e
Compare
Actually, I need to double check with performance folks if we are good to migrate the browser metrics from tags to attributes, not sure if something relies on these...! |
Only missing are browser metrics, where we need to verify this can be refactored already.
c237db8
to
deab246
Compare
I ended up extracting the browser metrics changes out into #10823, so we can already merge the "clearer" stuff. |
attributes: { | ||
from: currPathname, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lforst Just a reminder for ourselves during the v8 alpha: we need to review all our auto instrumentation for what attribute we set, what we actually need/want, etc.
Mostly, we rewrite this to just use attributes.
This affects esp.:
routing.instrumentation
type tags completely (this is covered by origin now anyhow)Not covered by this are browser metrics, which is a dedicated PR here: #10823