This repository was archived by the owner on Dec 5, 2025. It is now read-only.
Add OT-to-AO support for Method, Status, URL aggregate metrics feature #153
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.
When customers use our builtin http.Handler instrumentation, or call methods on ao.Trace() they get metrics aggregation for throughput, latency, and error counts aggregated by transaction name, HTTP method, and HTTP status.
This PR allows OpenTracing users to access those aggregation features by calling OT Span.SetTag() on
http.url,http.method, andhttp.status_code. (Support for setting transaction name for use in these metrics aggregations was part of #147, but did not cover HTTP method and status.)