Repository navigation
Converge Tracing/Profiling to Native Set of Hooks #729
Description
We are looking for users to document pseudo-APIs that demonstrate what they are looking in a tracing or profiling API. Please submit or link to documents with examples of what information you'd like to gather from the process, and potential APIs of how to do so.
Activity
trevnorris commentedon Feb 5, 2015
@thlorenz sent me this link to a header file in Chromium that has a tracing API: http://src.chromium.org/chrome/trunk/src/base/debug/trace_event.h
Qard commentedon Feb 5, 2015
My idea is roughly this: https://gist.github.com/Qard/3cc472d85c9a7277dee8
When the flag for the static probes is off, the
TRACE(...)andINSTRUMENT(...)macros would just do nothing, incurring no overhead. When turned on, it sets up a basic event emitter that third-party modules can listen for events from.The ALL aspect of it is just a convenience thing. It might be better to require explicit handlers for each event type.
trevnorris commentedon Feb 6, 2015
Information from @natduca #671 (comment)
GlenTiki commentedon Feb 6, 2015
Some thoughts, I think everyone is kinda thinking along the same lines:
https://gist.github.com/thekemkid/c51ed25eb3a5a603cb7e
sam-github commentedon Feb 16, 2015
https://github.com/strongloop/async-tracker#async-tracker-library
/cc @kraman
Trott commentedon Mar 11, 2016
@trevnorris Is this still an issue to keep open? Maybe the discussion has moved elsewhere? Looks like no one's added anything for about a year.
trevnorris commentedon Mar 11, 2016
@Trott Think we can. Between finalizing a public AsyncWrap API and the v8 tracing API seems decisions have been made.
Fishrock123 commentedon Jun 29, 2016
Closing as seems to be @trevnorris's reply.