Integrate database with OpenTelemetry in quarkus

[kavishkamk]

I am try to integrate quarkus application with OpenTelemetry. For that I want Instrumentation for JDBC. In the documentation https://quarkus.io/guides/opentelemetry#jdbc it mentions to use https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/jdbc/library#driver-way . But bucause of the project configuration I can use this. But in the documentation there is another way. https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/jdbc/library#datasource-way . How can I implement this solution in quarkus.

Can some one help me to this?

This is my liquibase runner file

package .....infrastructure.data;

import javax.enterprise.context.ApplicationScoped;
import javax.enterprise.event.Observes;

import io.quarkus.runtime.LaunchMode;
import org.eclipse.microprofile.config.inject.ConfigProperty;

import io.quarkus.runtime.StartupEvent;
import io.quarkus.runtime.util.ExceptionUtil;
import liquibase.Contexts;
import liquibase.LabelExpression;
import liquibase.Liquibase;
import liquibase.database.DatabaseConnection;
import liquibase.database.DatabaseFactory;
import liquibase.exception.LiquibaseException;
import liquibase.resource.ClassLoaderResourceAccessor;
import liquibase.resource.ResourceAccessor;
import io.quarkus.logging.Log;

@ApplicationScoped
public class LiquibaseRunner {

    @ConfigProperty(name = "quarkus.datasource.jdbc.url")
    String datasourceUrl;

    @ConfigProperty(name = "quarkus.datasource.username")
    String datasourceUsername;

    @ConfigProperty(name = "quarkus.datasource.password")
    String datasourcePassword;

    @ConfigProperty(name = "quarkus.liquibase.change-log")
    String changeLogLocation;

    public void onApplicationStart(@Observes StartupEvent even) {
        LaunchMode mode = io.quarkus.runtime.LaunchMode.current();
        if(mode != LaunchMode.TEST) {
            this.runMigration();
        } else {
            Log.info("Skipping DB migrations in TEST mode.");
        }
    }
    public void runMigration() {
        Log.info("Migrating DB " + datasourceUrl);
        Liquibase liquibase = null;
        try {
            ResourceAccessor resourceAccessor = new ClassLoaderResourceAccessor(Thread.currentThread().getContextClassLoader());
            DatabaseConnection conn = DatabaseFactory.getInstance().openConnection(datasourceUrl, datasourceUsername, datasourcePassword, null, resourceAccessor);

            liquibase = new Liquibase(changeLogLocation, resourceAccessor, conn);
            liquibase.update(new Contexts(), new LabelExpression());
        } catch (Exception e) {
            Log.error("Liquibase Migration Exception: " + ExceptionUtil.generateStackTrace(e));
        }
        finally {
            if(liquibase!=null)
            {
                try {
                    liquibase.close();
                } catch (LiquibaseException e) {
                    Log.info(e.getMessage());
                }
            }
        }
    }

     
}

[trask]

cc @michalvavrik @brunobat

[michalvavrik]

Cool, thanks!

[kavishkamk]

@brunobat Yes. I will link those questions with answers after solving It. Thank you..

[kavishkamk]

@michalvavrik The problem is in the project ( this is project developed by a team) they use reactive url and the jdbc driver url. Still, I didn't have a time to discuss about it. After it I will give a update. I will add the applicaiton.property file with this comment.

quarkus.datasource.reactive.url=vertx-reactive:postgresql://localhost/telemetry
quarkus.datasource.db-kind=postgresql
quarkus.datasource.jdbc.url=jdbc:postgresql://localhost:5432/telemetry
quarkus.datasource.password=fdfdfdfdf
quarkus.datasource.username=telemetry
quarkus.liquibase.change-log=db/changeLog.xml
quarkus.liquibase.migrate-at-start=true
quarkus.liquibase.default-schema-name=public
quarkus.hibernate-orm.log.sql=true
quarkus.hibernate-orm.database.generation=none

## with distributed tracing with OpenTelemetry
#quarkus.datasource.jdbc.url=jdbc:otel:postgresql://localhost:5432/telemetry
#quarkus.datasource.jdbc.driver=io.opentelemetry.instrumentation.jdbc.OpenTelemetryDriver

With this both configuration when I try to use jdbc.otel with the driver I can't use It. It throws error. In the stack overflow answer I think I can solve the problem. But before that I am waiting for dussuccstion to understand what they did and get some idea. I will give an update after it. Thank you

[michalvavrik]

Sure, I'll be very interested in details. To your example - using both reactive.url and jdbc.url seems wrong and I think OT driver way won't work with a reactive driver.

[kavishkamk]

Yes. I also think OT driver not work with reactive driver. I will give update