|
10 | 10 |
|
11 | 11 | Delivers a JSON-formatted diagnostic summary, written to a file.
|
12 | 12 |
|
13 |
| -The report is intended for development, test and production use, to capture |
| 13 | +The report is intended for development, test, and production use, to capture |
14 | 14 | and preserve information for problem determination. It includes JavaScript
|
15 | 15 | and native stack traces, heap statistics, platform information, resource
|
16 | 16 | usage etc. With the report option enabled, diagnostic reports can be triggered
|
@@ -508,9 +508,9 @@ the application, in expectation of self-adjusting the resource consumption,
|
508 | 508 | load balancing, monitoring etc.
|
509 | 509 |
|
510 | 510 | The content of the report consists of a header section containing the event
|
511 |
| -type, date, time, PID and Node.js version, sections containing JavaScript and |
| 511 | +type, date, time, PID, and Node.js version, sections containing JavaScript and |
512 | 512 | native stack traces, a section containing V8 heap information, a section
|
513 |
| -containing `libuv` handle information and an OS platform information section |
| 513 | +containing `libuv` handle information, and an OS platform information section |
514 | 514 | showing CPU and memory usage and system limits. An example report can be
|
515 | 515 | triggered using the Node.js REPL:
|
516 | 516 |
|
|
0 commit comments