Tracking language implementations

[jack-berg]

trafficstars

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

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

[marcalff]

For C++, current development is located here:

• https://github.com/open-telemetry/opentelemetry-cpp/pull/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 https://github.com/open-telemetry/opentelemetry-configuration/pull/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: https://github.com/open-telemetry/opentelemetry-python/pull/3632

[ocelotl]

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

[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.

[codeboten]

Thanks for the reminder @marcalff, updated the table

[codeboten]

@tsloughter is there a branch or pr for the work you've been doing in erlang?

[tsloughter]

@codeboten none yet. But since it is clear the cli is eventually to be merged once I work out all the issues I'll get started on it soon and update here when I have something pushed to a branch.

[pellared]

There is a WIP PR for .NET Automatic Instrumentation:

• https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/pull/4270

CC @ysolomchenko

[codeboten]

Updated the description to link to the dotnet PR and issue, thanks @pellared for the link!

[tsloughter]

I have a PR but I may change strategies. The issue is we already supported file configuration which complicates the integration, along with how we start things on boot. But to be complete, here is my PR https://github.com/open-telemetry/opentelemetry-erlang/pull/883

[jack-berg]

Hey SDK implementers - we have a new mechanism for tracking language implementation status in detail, which produces generated markdown here and like this:

If all the language maintainers can record / maintain their implementation status YAML file, we can close out this ticket and have a much more useful artifact to point users at.

For details see meta_schema_language_{language}.yaml.

For examples see #361 and #364.

This process and tooling is still very new so I'm open to feedback and evolving things to be as useful and easy as possible!