feat: add experimental http.{server/client}.request.duration metrics to instrumentation
#1785
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
Add optional OpenTelemetry HTTP metrics support for http.server.request.duration and http.client.request.duration while preserving backward compatibility for Ruby users until the metrics SDK matures.
Prometheus dashboard (metrics come from sinatra app that made net http request call)

initialize_metricshook that instrumentations should override to create instruments (e.g., counters, histograms).initialize_metricsis invoked frominstall.initialize_metricsdoes nothing.enable_metrics?, which considers configuration and an environment variable (metrics_env_var_value).{:metrics => true}) or env var.Metricsmodule that is prepended as a patch to record client request duration.EventHandlerWithMetricsandTracerMiddlewareWithMetricsto capture and record server-side request durations.Python and JS instrumentations require metrics; Ruby’s metrics SDK is still developing. This design records metrics safely without forcing changes to existing behavior or requiring a full SDK.