Converge Tracing/Profiling to Native Set of Hooks

[trevnorris]

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.

Tutorial on AsyncWrap

[trevnorris]

@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]

My idea is roughly this: https://gist.github.com/Qard/3cc472d85c9a7277dee8

When the flag for the static probes is off, the TRACE(...) and INSTRUMENT(...) 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]

Information from @natduca #671 (comment)

[GlenTiki]

Some thoughts, I think everyone is kinda thinking along the same lines:

https://gist.github.com/thekemkid/c51ed25eb3a5a603cb7e

[sam-github]

https://github.com/strongloop/async-tracker#async-tracker-library

/cc @kraman

[Trott]

@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]

@Trott Think we can. Between finalizing a public AsyncWrap API and the v8 tracing API seems decisions have been made.