Status
OpenTelemetry is made up of several components, some language-specific and others language-agnostic. When looking for a status, make sure to look for the status from the right component page. For example, the status of a signal in the specification may not be the same as the signal status in a particular language SDK.
Language SDKs
For the development status, or maturity level, of a language SDK, see the following table:
| Language | Traces | Metrics | Logs |
|---|---|---|---|
| C++ | Stable | Stable | Stable |
| C#/.NET | Stable | Stable | Stable |
| Erlang/Elixir | Stable | Experimental | Experimental |
| Go | Stable | Stable | In development |
| Java | Stable | Stable | Stable |
| JavaScript | Stable | Stable | Experimental |
| PHP | Stable | Stable | Stable |
| Python | Stable | Stable | Experimental |
| Ruby | Stable | In development | In development |
| Rust | Beta | Alpha | Alpha |
| Swift | Stable | Experimental | In development |
For more details on the specification compliance per implementation, see the Spec Compliance Matrix.
Collector
The collector status is: mixed, since core collector components currently have mixed stability levels.
Collector components differ in their maturity levels. Each component has its
stability documented in its README.md. You can find a list of all available
collector components in the registry.
Specifications
For the development status, or maturity level, of the specification, see the following: Specification Status Summary.