We are currently exploring open source options for dynamically instrumenting legacy Java platforms for a large commercial client. This project is currently the most interesting option, since it promises to be able to export the trace results to OpenTelemetry, which seems to be a new standard going forward. Unfortunately, the dependency on the java-opentelemetry-bridge trace exporter is out of date, and currently points at a version of the exporter which does not work as intended.
Currently, this Java agent is using version 0.2.0 of the OpenTelemetry Bridge Trace Exporter, which contains a bug regarding address port validation. This makes the exporter wholly unusable. See:
opentracing-contrib/java-opentelemetry-bridge#1
opentracing-contrib/java-opentelemetry-bridge#2
The bug is however, fixed in version 0.4.0. I hope that you will update this dependency for future releases. In the meantime, we will be using a custom-built jar.
We are currently exploring open source options for dynamically instrumenting legacy Java platforms for a large commercial client. This project is currently the most interesting option, since it promises to be able to export the trace results to OpenTelemetry, which seems to be a new standard going forward. Unfortunately, the dependency on the
java-opentelemetry-bridgetrace exporter is out of date, and currently points at a version of the exporter which does not work as intended.Currently, this Java agent is using version 0.2.0 of the OpenTelemetry Bridge Trace Exporter, which contains a bug regarding address port validation. This makes the exporter wholly unusable. See:
The bug is however, fixed in version 0.4.0. I hope that you will update this dependency for future releases. In the meantime, we will be using a custom-built jar.
@safris @malafeev