aliibii opened a new pull request, #12681:
URL: https://github.com/apache/apisix/pull/12681

   ### Description
   
   This commit adds plugin execution tracing capability to the OpenTelemetry 
plugin, allowing users to trace individual plugin phases (rewrite, access, 
header_filter, body_filter, log) as child spans of the main request trace.
   
   Changes:
   - Added trace_plugins configuration option to OpenTelemetry plugin (default: 
true)
   - Enhanced plugin execution with OpenTelemetry span creation and finishing
   - Added request context attributes to plugin spans
   - Updated documentation with examples and usage instructions
   - Added test suite for the new functionality
   
   Features:
   - Plugin Phase Tracing: Creates child spans for each plugin phase execution
   - Rich Context: Includes HTTP method, URI, hostname, user agent, route info, 
and service info
   - Configurable: Can be enabled/disabled via trace_plugins configuration
   - Proper Hierarchy: Plugin spans are correctly nested under main request 
spans
   - Error Handling: Proper error status and message propagation
   
   #### Which issue(s) this PR fixes:
   
   Resolves #12510
   
   <!--
   *Automatically closes linked issue when PR is merged.
   Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
   -->
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [X] I have explained the changes or the new features added to this PR
   - [X] I have added tests corresponding to this change
   - [X] I have updated the documentation to reflect this change
   - [X] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   <!--
   
   Note
   
   1. Mark the PR as draft until it's ready to be reviewed.
   2. Always add/update tests for any changes unless you have a good reason.
   3. Always update the documentation to reflect the changes made in the PR.
   4. Make a new commit to resolve conversations instead of `push -f`.
   5. To resolve merge conflicts, merge master instead of rebasing.
   6. Use "request review" to notify the reviewer after making changes.
   7. Only a reviewer can mark a conversation as resolved.
   
   -->
   


-- 
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