Deprecate Remaining Span class and interface fields

[Lms24]

I realized we still have a lot of fields on the Span class and interface that need to be deprecated.

Span Interface

Beta Give feedback

1. feat(core): Deprecate span startTimestamp & endTimestamp #10192
   +0
   
2. feat(core): Deprecate Span.status #10208
   +0
   
3. feat(core): Deprecate Span.isSuccess() in favor of reading span status #10213
   +0
   
4. feat(core): Deprecate Span.parentSpanId #10244
   +0
   
5. feat(types): Deprecate op on Span interface #10217
   +0
   
6. feat(core): Deprecate Span.origin in favor of sentry.origin attribute #10260
   +0
   
7. feat(core): Deprecate Span.setHttpStatus in favor of setHttpStatus #10268
   +0
   

Additional public Span class fields

Beta Give feedback

1. ref(core): Add missing class field deprecations #10187
   +0
   
2. Span.endTimestamp - same as Span.startTimestamp (via feat(core): Deprecate span startTimestamp & endTimestamp #10192)
3. chore(core): Mark Span.getSpanJSON method as internal #10197
   +0
   
4. feat(core): Deprecate Span.spanRecorder #10199
   +0
   
5. feat(core): Deprecate Span.op in favor of op attribute #10189
   +0
   

ref #10033

Related fields on other interfaces

Beta Give feedback

1. feat(core): Deprecate StartSpanOptions.origin in favour of passing attribute #10274
   +0
   
2. feat(core): Deprecate spanStatusfromHttpCode in favour of getSpanStatusFromHttpCode #10361
   +0
   

[lforst]

• setHttpStatus should probably stay? It's pretty useful and doesn't hurt, unless I am missing something. can probably just go.
• We have multiple instances where we (and our customers) set start- and endTimestamps. A getter like spanToJson doesn't help here as a migration path. @mydea Can you set the start and end timestamps on otel spans retroactively?
• spanRecorder can likely be deprecated and be an implementation detail on the span object/class itself.

The rest looks good to me 👍

[Lms24]

We have multiple instances where we (and our customers) set start- and endTimestamps. A getter like spanToJson doesn't help here as a migration path. @mydea Can you set the start and end timestamps on otel spans retroactively?

setting them via startSpan et al. should still work I think 🤔 ending would need to happen via span.end(endTimestamp)

IdleTransaction (soon to be IdleSpan) in browser adjusts the endTimestamp. I wonder if for this it's enough to make the timestamps of Span protected (so still remove them publicly).

[mydea]

yeah, retroactive update of start/end time is not possible. This needs to be rewritten to buffer the endtime somewhere (?) and set it - but I think I did this here already kind of #9972, so should work, I hope..!

[mydea]

I will deprecate the timestamps!