StarTrace/Meeting Notes
From RAD Lab
[edit]
June 14, 2006
Attendance: Rodrigo, James
Things that need to be done immediately:
- Modifications to existing XTrace library to record ID + parent.
- Look into using SWIG instead of rewriting XTrace library in Ruby/Java etc.
- Modify Ruby Webricks server to add *trace id in HTTP header
- Modify Rails to propagate *trace id (first try using thread-local variable)
- Modify Ruby logging to log *trace id.
[edit]
June 8, 2006
Attendance: Armando, Rodrigo, James and Peter
What is *(star)Trace? => a mechanism to do end to end request tracing with minimal or no changes to the application.
- horizontal slice: propagating annotations between machines of the form <myID, parentID>
- vertical slice: on each machine, do local logging injected with id and send logging info to central repository of the form <myId, parentId, machineId, localTS>.
(insert picture here)
How does it relate to XTrace? => XTrace aims at mechanisms to propagate metadata (the xtr_id) over different layers of the networking stack and across different machines. It deals with the APIs to do this.
Prototype version 0.9:
- lighttpd/webricks => Rails application => Ruby mysql/db connector
- put ReqIds in local logging
Maybe apache instead of lighthttpd, since we have a module that reads xtr-annotations.
Future version needs:
- apache, mysql, local buffering for report.
[edit]
Related Work
ARM is an industry standard that we should be aware of.
