Skip to main content
OpenTelemetry HTTP semantic conventions (SemConv) became stable in 2023.
For existing users, if your application uses any of the libraries listed below, be careful before upgrading. If you upgrade to a newer version that emits only the new HTTP semantic conventions, your application will start emitting the new attributes’ names, and likely break your downstream workflows that use the older semantic conventions. Read our blog post for more details on how this could impact your usage of Honeycomb.
Use the below tables by language to find impacted instrumentation packages, as published under the OpenTelemetry GitHub organization, and the current status of their compliance with the stable HTTP semantic conventions. Refer to the OpenTelemetry migration plan for details on how the OpenTelemetry Community is planning for users to handle this breaking change. In the tables below:
  • OTEL_SEMCONV_STABILITY_OPT_IN supported indicates the range of versions, if any, that support the OTEL_SEMCONV_STABILITY_OPT_IN environment variable.
  • http/dup supported indicates whether the library can be made to produce both old and stable semantic conventions.
  • Only Stable HTTP SemConv Emitted indicates the first version that only the new, stable HTTP semantic conventions can be emitted.

​
.NET

​
JavaScript

​
Python

​
Ruby

​
Go

Stable HTTP SemConv has been merged for all of the following Go instrumentation libraries and is awaiting release.

​
Java (agent instrumentation)

​
Java (library instrumentation)

​
PHP

The SemConv package with stable HTTP SemConv is available, but no PHP instrumentation libraries use it yet.