You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow the user to specify the filepath for the trace_events log file
using a template string.
PR-URL: #18480
Reviewed-By: Ali Ijaz Sheikh <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Copy file name to clipboardExpand all lines: doc/api/tracing.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,15 @@ Running Node.js with tracing enabled will produce log files that can be opened
33
33
in the [`chrome://tracing`](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool)
34
34
tab of Chrome.
35
35
36
+
The logging file is by default called `node_trace.${rotation}.log`, where
37
+
`${rotation}` is an incrementing log-rotation id. The filepath pattern can
38
+
be specified with `--trace-event-file-pattern` that accepts a template
39
+
string that supports `${rotation}` and `${pid}`. For example:
0 commit comments