From 19ee126668d5e24d500e45af425251a402689596 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Wed, 18 Jul 2018 11:02:14 -0400 Subject: [PATCH 1/9] doc: initial cut at support tiers for diag tools --- .../diagnostic-tooling-support-tiers.md | 115 ++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 doc/guides/diagnostic-tooling-support-tiers.md diff --git a/doc/guides/diagnostic-tooling-support-tiers.md b/doc/guides/diagnostic-tooling-support-tiers.md new file mode 100644 index 00000000000000..4b733a91a4cb64 --- /dev/null +++ b/doc/guides/diagnostic-tooling-support-tiers.md @@ -0,0 +1,115 @@ +# Diagnostic Tooling Support Tiers + +Diagnostic tooling is important to the consumers of Node.js. It is used both +in development and in production in order to investigate problems. The failure +of one of these tools may be as big a problem for an end user as a bug within +the runtime itself. + +The Node.js project has assessed the tools and the APIs which support those +tools. Each of the tools and APIs has been put them into one of +the following tiers. + +* Tier 1 - Mmust always be working for all + Current and LTS Node.js releases. A release will not be shipped if the test + suite for the tool/API is not green. To be considered for inclusion + in this tier it must have a good test suite and that test suite and a job + must exist in the Node.js CI so that it can be run as part of the release + process. No commit to master should break this tool/API if the next + release is within 1 month. + +* Tier 2 - Must be working for all + LTS releases. An LTS release will not be shipped if the test + suite for the tool/API is not green. To be considered for inclusion + in this tier it must have a good test suite and that test suite and a job + must exist in the Node.js CI so that it can be run as part of the release + process. + + * Tier 3 - If possible its test suite + will be run at least nightly in the Node.js CI and issues opened for + failures. Does not block shipping a release. + + * Tier 4 - Does not block shipping a release. + + * Unclassified - tool/API is new or does not have the required testing in the + Node.js CI in order to qualify for a higher tier. + +The choice of which tier a particular tool will be assigned to, will be a +collaborative decision between Diagnostics WG and Release WG. Some of the +criteria considered might be: + +* If the tool fits into a key cateogry as listed below. +* Whether the tool is actively used by the community. +* The Availability of alternatives. +* Impact to the overall ecosystem if the tool is not working. +* The availability of reliable test suite that can be integrated into our CI. +* The availability of maintainer or community collaborator who will help + resolve issues when there are CI failures. +* If the tool is maintained the Node.js foundation GitHub organization. + +The current categories of tools/APIs that fall under these Tiers are: + +* FDDC (F) - First failure data capture, Easy to consume initial diagnostic + information. +* Tracing (T) - use of logging to provide information about execution flow. +* Memory (M) - tools that provide additional information about memory + used in the Heap or by native code. +* Profiling (P) - tools that provide additional information about where + cpu cycles are being spent. +* AsyncFlow (A) - tools that provide additional insight into asynchronous + execution flow. + + +The following tools are currently assigned to Tiers as follows + +## Tier 1 + + | Tool Type | Tool Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + |-----------|---------------------------|-------------------------------|-------------------------|-------------| + | | | | | | + +## Tier 2 + + | Tool Type | Tool Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + |-----------|---------------------------|-------------------------------|-------------------------|-------------| + | | | | | | + + +## Tier 3 + + | Tool Type | Tool Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + |-----------|---------------------------|-------------------------------|-------------------------|-------------| + | | | | | | + +## Tier 4 + + | Tool Type | Tool Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + |-----------|---------------------------|-------------------------------|-------------------------|-------------| + | | | | | | + +## Not yet classified + + | Tool Type | Tool/API Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + |-----------|---------------------------|-------------------------------|-------------------------|-------------| + | FFDC | node-report | No | No | 1 | + | Memory | llnode | ? | No | 2 | + | Memory | mdb_V8 | No | No | 4 | + | Memory | node-heapdump | No | No | 2 | + | Memory | V8 heap profiler | No | Yes | 1 | + | Memory | V8 sampling heap profiler | No | Yes | 1 | + | AsyncFlow | Async Hooks(API) | ? | Yes | 1 | + | Debugger | V8 Debug protocol(API) | No | Yes | 1 | + | Debugger | Command line Debug Client | ? | Yes | 1 | + | Debugger | Chrome Dev tools | ? | No | 3 | + | Debugger | Chakracore - time-travel | No | data source only | to early | + | Tracing | trace_events(API) | No | Yes | 1 | + | Tracing | DTrace | No | Partial | 3 | + | Tracing | LTTng | No | Removed ? | N/A | + | Tracing | ETW | No | Partial | 3 | + | Profiling | V8 cpu profiler | No | Yes | 1 | + | Profiling | Linux perf | No | Partial | ? | + | Profiling | Windows xperf | No | ? | ? | + | Profiling | Ox | No | No | to early | + | Profiling | node-clinic | No | No | to early | + | F/P/T | appmetrics | No | No | ? | + | M/T | eBPF tracing tool | No | No | ? | + From 345d17f5689c23d4a46c2f531d30569d4f371768 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 7 Aug 2018 18:06:58 -0400 Subject: [PATCH 2/9] squash: partially address first set of comments --- .../diagnostic-tooling-support-tiers.md | 48 ++++++++++--------- 1 file changed, 25 insertions(+), 23 deletions(-) diff --git a/doc/guides/diagnostic-tooling-support-tiers.md b/doc/guides/diagnostic-tooling-support-tiers.md index 4b733a91a4cb64..4db89e729bb79a 100644 --- a/doc/guides/diagnostic-tooling-support-tiers.md +++ b/doc/guides/diagnostic-tooling-support-tiers.md @@ -6,18 +6,18 @@ of one of these tools may be as big a problem for an end user as a bug within the runtime itself. The Node.js project has assessed the tools and the APIs which support those -tools. Each of the tools and APIs has been put them into one of +tools. Each of the tools and APIs has been put into one of the following tiers. -* Tier 1 - Mmust always be working for all +* Tier 1 - Must always be working(CI tests passing) for all Current and LTS Node.js releases. A release will not be shipped if the test suite for the tool/API is not green. To be considered for inclusion in this tier it must have a good test suite and that test suite and a job must exist in the Node.js CI so that it can be run as part of the release process. No commit to master should break this tool/API if the next - release is within 1 month. + major release is within 1 month. -* Tier 2 - Must be working for all +* Tier 2 - Must be working(CI tests passing) for all LTS releases. An LTS release will not be shipped if the test suite for the tool/API is not green. To be considered for inclusion in this tier it must have a good test suite and that test suite and a job @@ -37,58 +37,58 @@ The choice of which tier a particular tool will be assigned to, will be a collaborative decision between Diagnostics WG and Release WG. Some of the criteria considered might be: -* If the tool fits into a key cateogry as listed below. +* If the tool fits into a key category as listed below. * Whether the tool is actively used by the community. -* The Availability of alternatives. +* The availability of alternatives. * Impact to the overall ecosystem if the tool is not working. * The availability of reliable test suite that can be integrated into our CI. * The availability of maintainer or community collaborator who will help resolve issues when there are CI failures. -* If the tool is maintained the Node.js foundation GitHub organization. +* If the tool is maintained by the Node.js Foundation GitHub organization. The current categories of tools/APIs that fall under these Tiers are: -* FDDC (F) - First failure data capture, Easy to consume initial diagnostic +* FFDC (F) - First failure data capture, easy to consume initial diagnostic information. * Tracing (T) - use of logging to provide information about execution flow. * Memory (M) - tools that provide additional information about memory used in the Heap or by native code. * Profiling (P) - tools that provide additional information about where - cpu cycles are being spent. + CPU cycles are being spent. * AsyncFlow (A) - tools that provide additional insight into asynchronous execution flow. -The following tools are currently assigned to Tiers as follows +The tools are currently assigned to Tiers as follows: ## Tier 1 - | Tool Type | Tool Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + | Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js | Target Tier | |-----------|---------------------------|-------------------------------|-------------------------|-------------| | | | | | | ## Tier 2 - | Tool Type | Tool Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + | Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js | Target Tier | |-----------|---------------------------|-------------------------------|-------------------------|-------------| | | | | | | ## Tier 3 - | Tool Type | Tool Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + | Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js | Target Tier | |-----------|---------------------------|-------------------------------|-------------------------|-------------| | | | | | | ## Tier 4 - | Tool Type | Tool Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + | Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js | Target Tier | |-----------|---------------------------|-------------------------------|-------------------------|-------------| | | | | | | ## Not yet classified - | Tool Type | Tool/API Name | Regular Testing In Node.js CI | Integrated with Node.js | Target Tier | + | Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js | Target Tier | |-----------|---------------------------|-------------------------------|-------------------------|-------------| | FFDC | node-report | No | No | 1 | | Memory | llnode | ? | No | 2 | @@ -96,19 +96,21 @@ The following tools are currently assigned to Tiers as follows | Memory | node-heapdump | No | No | 2 | | Memory | V8 heap profiler | No | Yes | 1 | | Memory | V8 sampling heap profiler | No | Yes | 1 | - | AsyncFlow | Async Hooks(API) | ? | Yes | 1 | - | Debugger | V8 Debug protocol(API) | No | Yes | 1 | + | AsyncFlow | Async Hooks (API) | ? | Yes | 1 | + | Debugger | V8 Debug protocol (API) | No | Yes | 1 | | Debugger | Command line Debug Client | ? | Yes | 1 | | Debugger | Chrome Dev tools | ? | No | 3 | - | Debugger | Chakracore - time-travel | No | data source only | to early | - | Tracing | trace_events(API) | No | Yes | 1 | + | Debugger | Chakracore - time-travel | No | Data source only | too early | + | Tracing | trace_events (API) | No | Yes | 1 | | Tracing | DTrace | No | Partial | 3 | - | Tracing | LTTng | No | Removed ? | N/A | + | Tracing | LTTng | No | Removed? | N/A | | Tracing | ETW | No | Partial | 3 | - | Profiling | V8 cpu profiler | No | Yes | 1 | + | Tracing | Systemtap | No | Partial | ? | + | Profiling | V8 CPU profiler (--prof) | No | Yes | 1 | | Profiling | Linux perf | No | Partial | ? | - | Profiling | Windows xperf | No | ? | ? | - | Profiling | Ox | No | No | to early | + | Profiling | DTrace | No | Partial | 3 | + | Profiling | Windows Xperf | No | ? | ? | + | Profiling | Ox | No | No | too early | | Profiling | node-clinic | No | No | to early | | F/P/T | appmetrics | No | No | ? | | M/T | eBPF tracing tool | No | No | ? | From 57bef970ac87cb445b19108668a5ddb6f8c78cbc Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 7 Aug 2018 18:11:58 -0400 Subject: [PATCH 3/9] squash: address more comments --- doc/guides/diagnostic-tooling-support-tiers.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/doc/guides/diagnostic-tooling-support-tiers.md b/doc/guides/diagnostic-tooling-support-tiers.md index 4db89e729bb79a..5c3003354b94a5 100644 --- a/doc/guides/diagnostic-tooling-support-tiers.md +++ b/doc/guides/diagnostic-tooling-support-tiers.md @@ -15,7 +15,10 @@ the following tiers. in this tier it must have a good test suite and that test suite and a job must exist in the Node.js CI so that it can be run as part of the release process. No commit to master should break this tool/API if the next - major release is within 1 month. + major release is within 1 month. In addition: + * The maintainers of the tool remain responsive when there are problems; + * The tool must be actively used by the ecosystem; and + * The tool must be heavily depended on. * Tier 2 - Must be working(CI tests passing) for all LTS releases. An LTS release will not be shipped if the test @@ -38,7 +41,7 @@ collaborative decision between Diagnostics WG and Release WG. Some of the criteria considered might be: * If the tool fits into a key category as listed below. -* Whether the tool is actively used by the community. +* Whether the tool is actively used by the ecosystem. * The availability of alternatives. * Impact to the overall ecosystem if the tool is not working. * The availability of reliable test suite that can be integrated into our CI. From 19120b2df26567c25ddb9b5431a54c7b32afc6ac Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 7 Aug 2018 18:14:23 -0400 Subject: [PATCH 4/9] squash: address additional comments. --- doc/guides/diagnostic-tooling-support-tiers.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/guides/diagnostic-tooling-support-tiers.md b/doc/guides/diagnostic-tooling-support-tiers.md index 5c3003354b94a5..1e62cf2993e4e3 100644 --- a/doc/guides/diagnostic-tooling-support-tiers.md +++ b/doc/guides/diagnostic-tooling-support-tiers.md @@ -17,9 +17,11 @@ the following tiers. process. No commit to master should break this tool/API if the next major release is within 1 month. In addition: * The maintainers of the tool remain responsive when there are problems; - * The tool must be actively used by the ecosystem; and - * The tool must be heavily depended on. - + * The tool must be actively used by the ecosystem; + * The tool must be heavily depended on; and + * The tool must only be using APIs exposed by Nodejs as opposed to + its dependencies. + * Tier 2 - Must be working(CI tests passing) for all LTS releases. An LTS release will not be shipped if the test suite for the tool/API is not green. To be considered for inclusion From c31bf8a504989e9d65e7ab794e1e51f1225538ba Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 7 Aug 2018 18:22:22 -0400 Subject: [PATCH 5/9] squash: address additional comments --- doc/guides/diagnostic-tooling-support-tiers.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/doc/guides/diagnostic-tooling-support-tiers.md b/doc/guides/diagnostic-tooling-support-tiers.md index 1e62cf2993e4e3..909cee12612f34 100644 --- a/doc/guides/diagnostic-tooling-support-tiers.md +++ b/doc/guides/diagnostic-tooling-support-tiers.md @@ -18,9 +18,13 @@ the following tiers. major release is within 1 month. In addition: * The maintainers of the tool remain responsive when there are problems; * The tool must be actively used by the ecosystem; - * The tool must be heavily depended on; and + * The tool must be heavily depended on; + * The tool must be work on all supported platforms; + * The tol must had a guide or other documentation in the Node.js GitHub + organization or website; * The tool must only be using APIs exposed by Nodejs as opposed to - its dependencies. + its dependencies; and + * The tool must be open source. * Tier 2 - Must be working(CI tests passing) for all LTS releases. An LTS release will not be shipped if the test @@ -96,7 +100,6 @@ The tools are currently assigned to Tiers as follows: | Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js | Target Tier | |-----------|---------------------------|-------------------------------|-------------------------|-------------| | FFDC | node-report | No | No | 1 | - | Memory | llnode | ? | No | 2 | | Memory | mdb_V8 | No | No | 4 | | Memory | node-heapdump | No | No | 2 | | Memory | V8 heap profiler | No | Yes | 1 | @@ -104,6 +107,7 @@ The tools are currently assigned to Tiers as follows: | AsyncFlow | Async Hooks (API) | ? | Yes | 1 | | Debugger | V8 Debug protocol (API) | No | Yes | 1 | | Debugger | Command line Debug Client | ? | Yes | 1 | + | Debugger | llnode | ? | No | 2 | | Debugger | Chrome Dev tools | ? | No | 3 | | Debugger | Chakracore - time-travel | No | Data source only | too early | | Tracing | trace_events (API) | No | Yes | 1 | @@ -115,7 +119,7 @@ The tools are currently assigned to Tiers as follows: | Profiling | Linux perf | No | Partial | ? | | Profiling | DTrace | No | Partial | 3 | | Profiling | Windows Xperf | No | ? | ? | - | Profiling | Ox | No | No | too early | + | Profiling | Ox | No | No | 4 | | Profiling | node-clinic | No | No | to early | | F/P/T | appmetrics | No | No | ? | | M/T | eBPF tracing tool | No | No | ? | From ee6b81d7d44f311bbae5f57d37d45578c0637771 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 7 Aug 2018 18:33:40 -0400 Subject: [PATCH 6/9] squash: address rest of comments --- .../diagnostic-tooling-support-tiers.md | 23 +++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-) diff --git a/doc/guides/diagnostic-tooling-support-tiers.md b/doc/guides/diagnostic-tooling-support-tiers.md index 909cee12612f34..e988d3afbca47d 100644 --- a/doc/guides/diagnostic-tooling-support-tiers.md +++ b/doc/guides/diagnostic-tooling-support-tiers.md @@ -16,12 +16,12 @@ the following tiers. must exist in the Node.js CI so that it can be run as part of the release process. No commit to master should break this tool/API if the next major release is within 1 month. In addition: - * The maintainers of the tool remain responsive when there are problems; + * The maintainers of the tool must remain responsive when there are problems; * The tool must be actively used by the ecosystem; * The tool must be heavily depended on; - * The tool must be work on all supported platforms; - * The tol must had a guide or other documentation in the Node.js GitHub + * The tool must have a guide or other documentation in the Node.js GitHub organization or website; + * The tool must be work on all supported platforms; * The tool must only be using APIs exposed by Nodejs as opposed to its dependencies; and * The tool must be open source. @@ -31,7 +31,13 @@ the following tiers. suite for the tool/API is not green. To be considered for inclusion in this tier it must have a good test suite and that test suite and a job must exist in the Node.js CI so that it can be run as part of the release - process. + process. In addition: + * The maintainers of the tool must remain responsive when there are problems; + * The tool must be actively used by the ecosystem; + * The tool must be heavily depended on; + * The tool must have a guide or other documentation in the Node.js GitHub + organization or website; + * The tool must be open source. * Tier 3 - If possible its test suite will be run at least nightly in the Node.js CI and issues opened for @@ -66,7 +72,16 @@ The current categories of tools/APIs that fall under these Tiers are: CPU cycles are being spent. * AsyncFlow (A) - tools that provide additional insight into asynchronous execution flow. + +## Adding a tool to this list +Any tool that might be used to investigate issues when running Node.js can be added to the +list. If there is a new tool that should be added to the list, it should start by being +added to the "Not yet classified" or "Tier 4" lists. Once it has been added to the list +"promotion" to Tier 3 through Tier 1 requires that the requirements listed above be met +AND have agreement from Diagnostics WG and Release WG based on the criteria listed above. + +# Tiers The tools are currently assigned to Tiers as follows: From bb4ec69a919a7b3e066dfbeb490ed51b2cfe3439 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Wed, 8 Aug 2018 16:50:48 -0400 Subject: [PATCH 7/9] squash: address comments --- doc/guides/diagnostic-tooling-support-tiers.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/guides/diagnostic-tooling-support-tiers.md b/doc/guides/diagnostic-tooling-support-tiers.md index e988d3afbca47d..32e833f76c5a0f 100644 --- a/doc/guides/diagnostic-tooling-support-tiers.md +++ b/doc/guides/diagnostic-tooling-support-tiers.md @@ -14,14 +14,15 @@ the following tiers. suite for the tool/API is not green. To be considered for inclusion in this tier it must have a good test suite and that test suite and a job must exist in the Node.js CI so that it can be run as part of the release - process. No commit to master should break this tool/API if the next - major release is within 1 month. In addition: + process. Tests on master will be run nightly when possible to provide early warning + of potential issues. No commit to the current and LTS release branches should break this + tool/API if the next major release is within 1 month. In addition: * The maintainers of the tool must remain responsive when there are problems; * The tool must be actively used by the ecosystem; * The tool must be heavily depended on; * The tool must have a guide or other documentation in the Node.js GitHub organization or website; - * The tool must be work on all supported platforms; + * The tool must be working on all supported platforms; * The tool must only be using APIs exposed by Nodejs as opposed to its dependencies; and * The tool must be open source. From 1e46bd30820de2ed7e3e811fd4f60d1a08197e49 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Thu, 9 Aug 2018 11:44:29 -0400 Subject: [PATCH 8/9] squash: fix linting issues from comments --- .../diagnostic-tooling-support-tiers.md | 27 +++++++++++-------- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/doc/guides/diagnostic-tooling-support-tiers.md b/doc/guides/diagnostic-tooling-support-tiers.md index 32e833f76c5a0f..2c9002de47cd12 100644 --- a/doc/guides/diagnostic-tooling-support-tiers.md +++ b/doc/guides/diagnostic-tooling-support-tiers.md @@ -14,10 +14,12 @@ the following tiers. suite for the tool/API is not green. To be considered for inclusion in this tier it must have a good test suite and that test suite and a job must exist in the Node.js CI so that it can be run as part of the release - process. Tests on master will be run nightly when possible to provide early warning - of potential issues. No commit to the current and LTS release branches should break this - tool/API if the next major release is within 1 month. In addition: - * The maintainers of the tool must remain responsive when there are problems; + process. Tests on master will be run nightly when possible to provide + early warning of potential issues. No commit to the current and LTS + release branches should break this tool/API if the next major release + is within 1 month. In addition: + * The maintainers of the tool must remain responsive when there + are problems; * The tool must be actively used by the ecosystem; * The tool must be heavily depended on; * The tool must have a guide or other documentation in the Node.js GitHub @@ -33,7 +35,8 @@ the following tiers. in this tier it must have a good test suite and that test suite and a job must exist in the Node.js CI so that it can be run as part of the release process. In addition: - * The maintainers of the tool must remain responsive when there are problems; + * The maintainers of the tool must remain responsive when + there are problems; * The tool must be actively used by the ecosystem; * The tool must be heavily depended on; * The tool must have a guide or other documentation in the Node.js GitHub @@ -76,13 +79,15 @@ The current categories of tools/APIs that fall under these Tiers are: ## Adding a tool to this list -Any tool that might be used to investigate issues when running Node.js can be added to the -list. If there is a new tool that should be added to the list, it should start by being -added to the "Not yet classified" or "Tier 4" lists. Once it has been added to the list -"promotion" to Tier 3 through Tier 1 requires that the requirements listed above be met -AND have agreement from Diagnostics WG and Release WG based on the criteria listed above. +Any tool that might be used to investigate issues when running Node.js can +be added to the list. If there is a new tool that should be added to the +list, it should start by being added to the "Not yet classified" or +"Tier 4" lists. Once it has been added to the list "promotion" to Tier 3 +through Tier 1 requires that the requirements listed above be met AND +have agreement from Diagnostics WG and Release WG based on the criteria +listed above. -# Tiers +## Tiers The tools are currently assigned to Tiers as follows: From 11bd549fb3dc676cca8afd3fd1f892268a056686 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Fri, 10 Aug 2018 16:28:47 -0400 Subject: [PATCH 9/9] squash: address comments --- doc/guides/diagnostic-tooling-support-tiers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/diagnostic-tooling-support-tiers.md b/doc/guides/diagnostic-tooling-support-tiers.md index 2c9002de47cd12..a23d5e52cd9336 100644 --- a/doc/guides/diagnostic-tooling-support-tiers.md +++ b/doc/guides/diagnostic-tooling-support-tiers.md @@ -140,7 +140,7 @@ The tools are currently assigned to Tiers as follows: | Profiling | Linux perf | No | Partial | ? | | Profiling | DTrace | No | Partial | 3 | | Profiling | Windows Xperf | No | ? | ? | - | Profiling | Ox | No | No | 4 | + | Profiling | 0x | No | No | 4 | | Profiling | node-clinic | No | No | to early | | F/P/T | appmetrics | No | No | ? | | M/T | eBPF tracing tool | No | No | ? |