db client metrics only makes sense with stable semconv

Author: zeitlinger

instrumentation-api-incubator/src/main/java/io/opentelemetry/instrumentation/api/incubator/semconv/db/DbClientMetrics.java

@@ -18,6 +18,7 @@
 import io.opentelemetry.instrumentation.api.instrumenter.OperationListener;
 import io.opentelemetry.instrumentation.api.instrumenter.OperationMetrics;
 import io.opentelemetry.instrumentation.api.internal.OperationMetricsUtil;
+import io.opentelemetry.instrumentation.api.internal.SemconvStability;
 import java.util.concurrent.TimeUnit;
 import java.util.logging.Logger;
 
@@ -44,7 +45,10 @@ public final class DbClientMetrics implements OperationListener {
    * @see InstrumenterBuilder#addOperationMetrics(OperationMetrics)
    */
   public static OperationMetrics get() {
-    return OperationMetricsUtil.create("database client", DbClientMetrics::new);
+    if (SemconvStability.emitStableDatabaseSemconv()) {
+      return OperationMetricsUtil.create("database client", DbClientMetrics::new);
+    }
+    return meter -> OperationMetricsUtil.NOOP_OPERATION_LISTENER;
   }
 
   private final DoubleHistogram duration;

instrumentation-api/src/main/java/io/opentelemetry/instrumentation/api/internal/OperationMetricsUtil.java

@@ -23,7 +23,7 @@
  */
 public class OperationMetricsUtil {
   private static final Logger logger = Logger.getLogger(OperationMetricsUtil.class.getName());
-  private static final OperationListener NOOP_OPERATION_LISTENER =
+  public static final OperationListener NOOP_OPERATION_LISTENER =
       new OperationListener() {
 
         @Override