feat: add plugin execution tracing to OpenTelemetry plugin #12681
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.
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:
New OpenTelemetry API functions available to plugins via
api_ctx.otel:api_ctx.otel.start_span(span_info)- Create custom spansapi_ctx.otel.stop_span(span_ctx, error_msg)- Finish spans with error handlingapi_ctx.otel.current_span()- Get current span contextapi_ctx.otel.get_plugin_context(plugin_name, phase)- Get plugin phase span contextapi_ctx.otel.with_span(span_info, fn)- Create span, execute function, and automatically finish spanspan_ctxas its first parameter, allowing access to the span for setting attributesFeatures:
with_spanprovides automatic span lifecycle management with error handlingWhich issue(s) this PR fixes:
Resolves #12510
Checklist