You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, we are preparing to migrate our entire backend vert.x based custom framework as a payment company based on Turkey.
However we have a major issue regarding to integrate trace applications such as dynatrace, datadog or equivalent. Messages goes through event bus seems untracable and since our operations are mission critic, we required to integrate a tracing applications to our systems. Our team on hard schedule migrating our entire legacy backend as well as maintaining legacy backend so we are unable to contribute development process for this feature.
The text was updated successfully, but these errors were encountered:
Well we do tried open telemetry. However library we are using rx-java (spesifically: lastest version of https://mvnrepository.com/artifact/io.vertx/vertx-rx-java) is not supporting open telemetry either. (or vice versa) We are unable to trace request in single trace and its spans, we receive multiple traces scattered unable to tell their parents which makes request practically untracable.
We had tried multiple open sourced telemetry platform none of them worked.
isimsizolan
changed the title
Easy integration of trace applications such as dynatrace, datadog or open source alternatives
Trace applications does not work as expected when Vertx Rx Java used. (dynatrace, datadog, open telemetry etc)
Aug 30, 2024
Hello, we are preparing to migrate our entire backend vert.x based custom framework as a payment company based on Turkey.
However we have a major issue regarding to integrate trace applications such as dynatrace, datadog or equivalent. Messages goes through event bus seems untracable and since our operations are mission critic, we required to integrate a tracing applications to our systems. Our team on hard schedule migrating our entire legacy backend as well as maintaining legacy backend so we are unable to contribute development process for this feature.
The text was updated successfully, but these errors were encountered: