@@ -21,7 +21,7 @@ back in to the CTC.
21
21
* [ Website] ( #website )
22
22
* [ Streams] ( #streams )
23
23
* [ Build] ( #build )
24
- * [ Tracing ] ( #tracing )
24
+ * [ Diagnostics ] ( #diagnostics )
25
25
* [ i18n] ( #i18n )
26
26
* [ Evangelism] ( #evangelism )
27
27
* [ Roadmap] ( #roadmap )
@@ -81,17 +81,22 @@ Its responsibilities are:
81
81
* Creates and manages build-containers.
82
82
83
83
84
- ### [ Tracing ] ( https://github.com/nodejs/tracing-wg )
84
+ ### [ Diagnostics ] ( https://github.com/nodejs/diagnostics )
85
85
86
- The tracing working group's purpose is to increase the
87
- transparency of software written in Node.js.
86
+ The diagnostics working group's purpose is to surface a set of comprehensive,
87
+ documented, and extensible diagnostic interfaces for use by
88
+ Node.js tools and JavaScript VMs.
88
89
89
90
Its responsibilities are:
90
- * Collaboration with V8 to integrate with ` trace_event ` .
91
- * Maintenance and iteration on AsyncWrap.
92
- * Maintenance and improvements to system tracing support (DTrace, LTTng, etc.)
93
- * Documentation of tracing and debugging techniques.
94
- * Fostering a tracing and debugging ecosystem.
91
+
92
+ * Collaborate with V8 to integrate ` v8_inspector ` into Node.js.
93
+ * Collaborate with V8 to integrate ` trace_event ` into Node.js.
94
+ * Collaborate with Core to refine ` async_wrap ` and ` async_hooks ` .
95
+ * Maintain and improve OS trace system integration (e.g. ETW, LTTNG, dtrace).
96
+ * Document diagnostic capabilities and APIs in Node.js and its components.
97
+ * Explore opportunities and gaps, discuss feature requests, and address
98
+ conflicts in Node.js diagnostics.
99
+ * Foster an ecosystem of diagnostics tools for Node.js.
95
100
96
101
### i18n
97
102
0 commit comments