[trace_event] tracking issue
joshgav opened this issue · comments
This issue is to track ongoing work to refine Trace Events in Node and graduate it from experimental state.
It builds on and replaces
Initial Trace PR including discussion: node#9304
todo:
- configurable output destinations
- support targeting lttng, etw, dtrace, etc...
- add a listener system (#81)
- C/C++ API (#83)
- JavaScript API (node-eps#48)
- needs to be as fast as possible, probably a VM intrinsic.
- add trace points to nodejs/node (#82)
- move existing dtrace/lttng trace writes to trace_event
- add trace points: async hooks (PR: nodejs/node#15538)
- relationship to upstream
trace_event_common.h(see nodejs/node#10628) - recommendations for naming categories for ecosystem
- need approach on how to collect "context"
- e.g., for capturing http connection info, currently connection object is passed through DTrace APIs, and some handler/provider, and then the handler/provider will navigate connection object to pull out interesting data to trace. This approach is brittle (dependent on structure of connection object), and puts burden on provider (ie., won't easily allow using different event tracing systems like lttng, dtrace,...).
- standardize on output format for trace event data
- command-line options to support tracing features.
I would like to bring an issue that i have found while playing with the runtime toggle of the trace events (via the inspector) : nodejs/node#23185
should this remain open? [ I am trying to chase dormant issues to closure ]
Yes, this is not yet completed
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.
Keeping this open, but we need to triage the todo list to identify which items were completed, which items are not relevant anymore, and any missing items.
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.