summaryrefslogtreecommitdiff
path: root/doc/api/tracing.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/api/tracing.md')
-rw-r--r--doc/api/tracing.md18
1 files changed, 16 insertions, 2 deletions
diff --git a/doc/api/tracing.md b/doc/api/tracing.md
index 67b3394d55..3a534177a3 100644
--- a/doc/api/tracing.md
+++ b/doc/api/tracing.md
@@ -10,8 +10,20 @@ 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.
+names.
+
+The available categories are:
+
+* `node`
+* `node.async_hooks` - Enables capture of detailed async_hooks trace data.
+* `node.perf` - Enables capture of [Performance API] measurements.
+ * `node.perf.usertiming` - Enables capture of only Performance API User Timing
+ measures and marks.
+ * `node.perf.timerify` - Enables capture of only Performance API timerify
+ measurements.
+* `v8`
+
+By default the `node`, `node.async_hooks`, and `v8` categories are enabled.
```txt
node --trace-events-enabled --trace-event-categories v8,node,node.async_hooks server.js
@@ -24,3 +36,5 @@ 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.
+
+[Performance API]: perf_hooks.html