[Docs]: Getting Started example uses deprecated `logging` exporter value; Java config docs missing `console` for metrics`

[FlowBreeze]

What needs to be changed?

Description

There are two related documentation inconsistencies found in the Java section:

Issue 1: Getting Started uses deprecated logging exporter value

The Getting Started by Example page uses the following environment variable configuration:

OTEL_TRACES_EXPORTER=logging \
OTEL_METRICS_EXPORTER=logging \
OTEL_LOGS_EXPORTER=logging

However, according to the OTel specification, "logging" is a deprecated value left for backwards compatibility and SHOULD NOT be supported by new implementations. The recommended replacement is "console".

Issue 2: otel.metrics.exporter does not list console as a known value

The Java SDK configuration page lists the known values for otel.metrics.exporter as only: otlp, prometheus, none.

The value console is not listed, unlike otel.traces.exporter and otel.logs.exporter which do include console (or logging-otlp). This creates confusion when trying to use a console/logging exporter for metrics in Java.

Expected behavior

1. The Getting Started example should either use console instead of logging, or include a note that logging is deprecated.
2. The Java configuration docs should clarify whether console is a valid value for otel.metrics.exporter, and if so, add it to the known values list.

References

• https://opentelemetry.io/docs/languages/java/getting-started/#instrumentation
• https://opentelemetry.io/docs/languages/java/configuration/#properties-exporters
• https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#exporter-selection

Name + path of the page

docs/languages/java/getting-started/

Additional context

No response

[tiffany76]

Hi @FlowBreeze, thanks for reporting your issue.

@open-telemetry/java-approvers, PTAL.