Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Refactor the CSpan objects

Description

Some of the fields (globalid, localid) should only really be present in the server objects. Worth taking the time to check all the members are in the right place, to avoid duplication, but also to make it clear where the data belongs.

Conclusion

None

Activity

Show:

Rodrigo Pastrana 
November 20, 2023 at 4:03 PM

If you can tackle this one, I can spend that time adding timing attributes to the span log output instead?  

Gavin Halliday 
November 17, 2023 at 1:45 PM

This should also

i) remove the traceName field from all spans

ii) have the trace manager create the tracer once, and pass it into the constructor of the CServerSpan

iii) Only store the tracer in the server span.

 

do you want to make this set of changes, or shall I and you review it?

 

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Pull Request URL

Created November 2, 2023 at 1:41 PM
Updated November 28, 2023 at 2:12 PM
Resolved November 28, 2023 at 2:12 PM

Flag notifications