- Assertion Testing
- Async Hooks
- Buffer
- C++ Addons
- C/C++ Addons - N-API
- Child Processes
- Cluster
- Command Line Options
- Console
- Crypto
- Debugger
- Deprecated APIs
- DNS
- Domain
- ECMAScript Modules
- Errors
- Events
- File System
- Globals
- HTTP
- HTTP/2
- HTTPS
- Inspector
- Internationalization
- Modules
- Net
- OS
- Path
- Performance Hooks
- Process
- Punycode
- Query Strings
- Readline
- REPL
- Stream
- String Decoder
- Timers
- TLS/SSL
- Tracing
- TTY
- UDP/Datagram
- URL
- Utilities
- V8
- VM
- ZLIB
Node.js v10.0.0-nightly20180201ad94be84f9 Documentation
Table of Contents
Tracing#
Trace Event provides a mechanism to centralize tracing information generated by V8, Node core, and userspace code.
Tracing can be enabled by passing the --trace-events-enabled flag when starting a
Node.js application.
The set of categories for which traces are recorded can be specified using the
--trace-event-categories flag followed by a list of comma separated category names.
By default the node, node.async_hooks, and v8 categories are enabled.
node --trace-events-enabled --trace-event-categories v8,node,node.async_hooks server.js
Running Node.js with tracing enabled will produce log files that can be opened
in the chrome://tracing
tab of Chrome.
Starting with Node 10.0.0, the tracing system uses the same time source as the
one used by process.hrtime() however the trace-event timestamps are expressed
in microseconds, unlike process.hrtime() which returns nanoseconds.