@brunobat from the Quarkus team is working on a comprehensive guide to document the migration from OpenTracing to OpenTelemetry in the context of Quarks 3 applications. @dymurray I think this could be a good candidate for our team to try to produce rules based on documentation about a given migration path. Most if not all of the contents in the guide refer to Quarkus specifics, but I think it would also be interesting to try to figure out if we can extract some generic guidelines that could apply to other runtimes like Spring boot (there is a generic migration guide here), and then provide the runtime specific recommendations based on the source technology of the application.
@brunobat from the Quarkus team is working on a comprehensive guide to document the migration from OpenTracing to OpenTelemetry in the context of Quarks 3 applications. @dymurray I think this could be a good candidate for our team to try to produce rules based on documentation about a given migration path. Most if not all of the contents in the guide refer to Quarkus specifics, but I think it would also be interesting to try to figure out if we can extract some generic guidelines that could apply to other runtimes like Spring boot (there is a generic migration guide here), and then provide the runtime specific recommendations based on the source technology of the application.