[#noissue]Add recoder HTTP messages #9940
Open
+4,178
−83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The collection of HTTP messages has been implemented, including but not limited to request headers, request bodies, response headers, response bodies, request URLs, etc.
HTTP message collection data is sent through the spanWebInfo extension object, reusing the sending port of the span data. Whether to collect webinfo and the webinfo sampling strategy can be configured in the configuration file. It supports truncation of message data to prevent UDP protocol transmission failures caused by excessively large data packets; it also supports exception judgement of response messages, which can be used for aggregated analysis.
Limitations:
① Currently, only agent data supports sending using the Thrift protocol, and gRPC is not supported at present;
② The collection of request URLs and headers, as well as response headers, depends on the client service running on Tomcat, Jetty, or Undertow containers;
③ The collection of request bodies and response bodies depends on the service using the Spring framework.