Tracking language implementations

[jack-berg]

This is a tracking issue for status of language implementations of file configuration

Language	Status	opentelemetry-configuration version	Notes
C++	Development	1.0.0-rc.1	open-telemetry/opentelemetry-cpp#2518
C#/.NET			open-telemetry/opentelemetry-dotnet-instrumentation#4270 open-telemetry/opentelemetry-dotnet#6380
Erlang	Development	1.0.0-rc.1
Go	Development	0.3.0	https://pkg.go.dev/go.opentelemetry.io/contrib/otelconf
Java	Development	1.0.0-rc.1	Available for use via opentelemetry-sdk-extension-incubator. Bundled with the otel java agent. Project Board
Javascript	Development	1.0.0-rc.1	Project Board
PHP	Development	0.4.0	SDK https://github.com/open-telemetry/opentelemetry-php/tree/main/src/Config/SDK. instrumentation config: open-telemetry/opentelemetry-php#1304
Python	Development		open-telemetry/opentelemetry-python#3632
Ruby
Rust
Swift

[marcalff]

For C++, current development is located here:

• [CONFIGURATION] Implement declarative configuration (config.yaml) opentelemetry-cpp#2518

[brettmc]

For PHP:

• we have merged but not publicly released file-based SDK configuration using version 0.1 (status=development)
• we are waiting on a 0.3 release to merge file-based instrumentation configuration (status=development)

[pellared]

For Go (developed mainly by @codeboten):

• contrib package: go.opentelemetry.io/contrib/config
• docs: https://pkg.go.dev/go.opentelemetry.io/contrib/config
• otel-config version: 0.2.0
• Status: Development
• notes: No examples, does not do env var substitution, other missing features.

[tsloughter]

Note: Erlang is waiting on #94

[jack-berg]

@ocelotl do you know the status of the python implementation you were working on? Where does the source code live?

[codefromthecrypt]

@jack-berg I assume this is only about file configuration, if so maybe change the title? if it is language in general of WIP specs, we can probably contribute stuff about event API into this one. Lemme know which way is intended.

[jack-berg]

It's specific to file configuration, but we're in the opentelemetry-configuration repo so we're already scoped to the file config portion of the spec. A more specific name could still be useful in project boards of issues where the repo isnt prevalent in the display.

[codefromthecrypt]

sorry I missed the repo name. My mistake

[jack-berg]

FYI, here's the PR with the in-progress python implementation: open-telemetry/opentelemetry-python#3632

[ocelotl]

Hello, @jack-berg I am working on the Python implementation again after a long time ✌️

[marcalff]

Now that there is some feedback on this for tracking, could the table itself be updated (because "we" do not have access right to do so) ?

Thanks.