add console as a supported env variable exporter type

[codeboten]

Changes

This PR is a follow up to #3740 and #3741. As some languages (the ones I looked at were: python, js, ruby) already support the console type of exporter, I thought it would be good if the spec confirmed it.

• CHANGELOG.md file updated for non-trivial changes

Keeping in draft until the other PRs are reviewed.

[pellared]

Just the changelog entry should be moved

[codeboten]

Note to reviewers that console is used in python, js, ruby. Java uses logging but after a brief chat w/ @jack-berg, he suggested adding an alias for console in java would be trivial.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[codeboten]

Not stale, but still blocked by #3740 and #3741.

[svrnm]

For completness:

Following the spec compliance matrix the following languages have support for OTEL_TRACES_EXPORTER and besides I listed how an enduser can set the console exporter:

• Java: logging
• JS: console
• Python: console
• Ruby: console
• Erlang: no "console" support yet
• PHP: console

Rust, C++, Go and Swift are listed with not supported/unknown. .NET is also listed as not supported, but the .NET auto instrumentation has the following construct (see https://opentelemetry.io/docs/instrumentation/net/getting-started/ & https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/docs/config.md#internal-logs):

OTEL_TRACES_EXPORTER=none \
  OTEL_METRICS_EXPORTER=none \
  OTEL_LOGS_EXPORTER=none \
  OTEL_DOTNET_AUTO_TRACES_CONSOLE_EXPORTER_ENABLED=true \
  OTEL_DOTNET_AUTO_METRICS_CONSOLE_EXPORTER_ENABLED=true \
  OTEL_DOTNET_AUTO_LOGS_CONSOLE_EXPORTER_ENABLED=true

[pellared]

Go will add support for console via autoexport thanks to open-telemetry/opentelemetry-go-contrib#4486 (not released yet)

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.