wu-sheng commented on code in PR #625:
URL: https://github.com/apache/skywalking-java/pull/625#discussion_r1375379288


##########
docs/en/setup/service-agent/java-agent/Optional-plugins.md:
##########
@@ -23,4 +23,5 @@ Now, we have the following known optional plugins.
 * Plugin of Apache ShenYu(incubating) Gateway 2.4.x in optional plugin folder. 
Please only activate this plugin when you install agent in Apache ShenYu 
Gateway.
 * Plugin of trace sampler CPU policy in the optional plugin folder. Please 
only activate this plugin when you need to disable trace collecting when the 
agent process CPU usage is too high(over threshold).
 * Plugin for Spring 6.x and RestTemplate 6.x are in the optional plugin 
folder. Spring 6 requires Java 17 but SkyWalking is still compatible with Java 
8. So, we put it in the optional plugin folder.
-* Plugin of nacos-client 2.x lib in optional plugin folder.The reason is many 
business irrelevant traces are generated, which cause extra payload to agents 
and backends, also spend more CPU, memory and network.
\ No newline at end of file
+* Plugin of nacos-client 2.x lib in optional plugin folder.The reason is many 
business irrelevant traces are generated, which cause extra payload to agents 
and backends, also spend more CPU, memory and network.
+* Plugin of netty-http 4.1.x lib in optional plugin folder.The reason is some 
frameworks use netty as an HTTP server and also enhanced by other plugins of 
SkyWalking, which can result in double trace collection

Review Comment:
   ```suggestion
   * Plugin of nacos-client 2.x lib in optional plugin folder. The reason is 
many business irrelevant traces are generated, which cause extra payload to 
agents and backends, also spend more CPU, memory and network.
   * Plugin of netty-http 4.1.x lib in optional plugin folder. The reason is 
some frameworks use Netty HTTP as kernel, which could double the unnecessary 
spans and create incorrect RPC relative metrics.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to