opentelemetry-instrumentation-http_client

OpenTelemetry HttpClient Instrumentation

The HttpClient instrumentation is a community-maintained instrumentation for the HttpClient gem.

How do I get started?

Install the gem using:

gem install opentelemetry-instrumentation-http_client

Or, if you use bundler, include opentelemetry-instrumentation-http_client in your Gemfile.

Usage

To use the instrumentation, call use with the name of the instrumentation:

OpenTelemetry::SDK.configure do |c|
  c.use 'OpenTelemetry::Instrumentation::HttpClient'
end

Alternatively, you can also call use_all to install all the available instrumentation.

OpenTelemetry::SDK.configure do |c|
  c.use_all
end

Examples

Example usage can be seen in the ./example/trace_demonstration.rb file

How can I get involved?

The opentelemetry-instrumentation-http_client gem source is on github, along with related gems including opentelemetry-api and opentelemetry-sdk.

The OpenTelemetry Ruby gems are maintained by the OpenTelemetry Ruby special interest group (SIG). You can get involved by joining us on our GitHub Discussions, Slack Channel or attending our weekly meeting. See the meeting calendar for dates and times. For more information on this and other language SIGs, see the OpenTelemetry community page.

License

The opentelemetry-instrumentation-http_client gem is distributed under the Apache 2.0 license. See LICENSE for more information.

HTTP semantic convention stability

In the OpenTelemetry ecosystem, HTTP semantic conventions have now reached a stable state. However, the initial HttpClient instrumentation was introduced before this stability was achieved, which resulted in HTTP attributes being based on an older version of the semantic conventions.

To facilitate the migration to stable semantic conventions, you can use the OTEL_SEMCONV_STABILITY_OPT_IN environment variable. This variable allows you to opt-in to the new stable conventions, ensuring compatibility and future-proofing your instrumentation.

When setting the value for OTEL_SEMCONV_STABILITY_OPT_IN, you can specify which conventions you wish to adopt:

• http - Emits the stable HTTP and networking conventions and ceases emitting the old conventions previously emitted by the instrumentation.
• http/dup - Emits both the old and stable HTTP and networking conventions, enabling a phased rollout of the stable semantic conventions.
• Default behavior (in the absence of either value) is to continue emitting the old HTTP and networking conventions the instrumentation previously emitted.

During the transition from old to stable conventions, HttpClient instrumentation code comes in three patch versions: dup, old, and stable. These versions are identical except for the attributes they send. Any changes to HttpClient instrumentation should consider all three patches.

For additional information on migration, please refer to our documentation.