-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynatrace One Agent: Traces not exported without @opentelemetry/exporter-trace-otlp-proto #274
Comments
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. |
what is the name of your ups? best, |
yeah, sorry, that was a late hour brain fart. the name doesn't matter. 😅 do you get this log output? telemetry/lib/tracing/index.js Line 153 in 67933be
if so, i'm afraid i can't assist any further. best, |
Hi @sjvans, No I can't see this message. And regarding one agent, I can find only these messages: But this is normal since we put the dependency telemetry/lib/tracing/index.js Line 150 in 67933be
We came back to the original question ;) |
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 ?
The text was updated successfully, but these errors were encountered: