t2t2

Lack of changes in fetch instrumentation actually brings up a small but significant difference in the ignoreUrls config option of XHR and fetch instrumentations In fetch instrumentation already parsed URL...

> I don't believe conforms to the general rational for spans having events Isn't it a bit premature to claim spans with events to hold timing information over SpanEvents when...

> Just to be clear, the ask here is to use a SINGLE Span.Event instead of multiple, and not a standalone Event. Ah yeah, using span.event attributes does have a...

Clarify of what you mean by scope, I assume InstrumentationScope since it's the only currently existing scope with attributes? (ignoring context-scoped attributes proposal as it's a proposal as frozen as...

It'd make sense when considering attribute priority, tho am a bit afraid that once one solution is out there, someone will hardcode their processing to specific scope level and then...

Was brought up in sig today, already fixed in #2610 (10 Nov 2021) separate question about how good current logic is (as in when enable should be called, during instrumentation...

Maybe consider having xhr (or fetch considering how it's available in node v18+, deno v1 and usually polyfilled in IE) as the default method in general and navigator.sendBeacon as backup...

FYI @cedricziel as you expressed interest in writing a proposal for this [in slack before](https://cloud-native.slack.com/archives/C0239SYARD2/p1700908968616519)

Hmm, if a password reset page is added it could be enough to reuse current users

The quick and dirty way if you don't mind leaving vuex to use this: ``` js // component.js export default { store, // or in a parent component vuex: {...