Dynatrace One Agent: Traces not exported without @opentelemetry/exporter-trace-otlp-proto

[sebastien-savalle]

Hello,

According to the documentation, it is recommended to let the Dynatrace OneAgent collect and export traces created by the library in order to provide a better experience.
We have a cloud foundry application running on SAP BTP with Dynatrace OneAgent enabled.
We can see detailed traces when the dependency @opentelemetry/exporter-trace-otlp-proto is present including traces related to Hana (cap-js/hana).
But we can't see details when we remove the dependency @opentelemetry/exporter-trace-otlp-proto. Only http requests are captured without sub traces (db, manual trace...)

Is there any requirements regarding the service binding ? We use a user-provided-service to share the dynatrace instance across cf spaces.

In addition, could you explain what are the differences between traces exported by one agent and the ones exported by OpenTelemetry ?

[yevgentrukhin]

I believe @opentelemetry/exporter-trace-otlp-proto would be needed if you plan on ingesting via OTEL to Dynatrace with 'telemetry-to-dynatrace'. Is that what you want to do? If not, oneAgent is extracting and showing OTEL instrumented traces without direct OTEL ingestion and it combines its own extracted traces with OTEL instrumented ones. If you want I can show it supposed to work in offline.