@link04 can you fill this in

We published docs for metrics:https://ddtrace.readthedocs.io/en/latest/api.html?highlight=opentelemetry#metrics

I can also fill this out in a bit

Do you think it's necessary to explain the fact that some languages need the exporter and some don't on this page?

You'll get the correct instructions on each language page, so I'm wondering if it's confusing to explain this here. Or another way: it's not going to affect any choice you make from this page.

(Also I think for Python the Exporter is only required for Logs/Metrics not Traces, so arguably it's confusing to say you need the Exporter for Python here.)

Good point! I agree that it's better to omit this. It adds unnecessary confusion when a user would just be guided to their specific page anyways.

We have steps in the setup for installing the SDK and Exporter, so it could be confusing to have them as prerequisites as well?

We also say in a note in the Overview section that you need the SDK and Exporter - I'm not sure we need that note either. (The note makes sense for the other languages where we're sayingnot to install the SDK/Exporter)

(Example needs completing)

Can we show the default for Python here?

I ended up removing this content from the language-specific pages in favor of the centralized environment variable config page (to avoid duplicating). What do you think? (We could add the details per SDK here too).

Should this also say to configure the Agent to not tail the application log file? Otherwise the logs will be duplicated - we say this on the .NET page.

We should also includeDD_TRACE_OTEL_ENABLED in this section

Added! Is the default for this true since it maps to !OTEL_SDK_DISABLED, which is false by default?

Note: Also applied your other suggestions to the config page. Thanks!

I like this breakdown for ENV and VERSION. Can we also include SERVICE here in this same block? TheOTEL_SERVICE_NAME environment variable still deserves a mention but I think having the key UST info all here would be more clear.

What do you think of linking out to OpenTelemetry to describe this? With this specific page linked:https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/otlp/#additional-environment-variable-configuration

We should link to our documentation for why it's the Datadog-recommended configuration:https://docs.datadoghq.com/opentelemetry/guide/otlp_delta_temporality/

I think we should revert to the previous description while also adding theservice.name resource attribute info to theOTEL_RESOURCE_ATTRIBUTES description later.

This is resolved as a resource attribute, not fromOTEL_SERVICE_NAME.
I'm not sure where this info came from, butOTEL_SERVICE_NAMEis responsible for setting theservice.name resource attribute. It's a little weird because in our traces we don't really use resource attributes, but in our metrics and logs we do.