Merge branch 'main' of github.com:open-telemetry/opentelemetry-java-instrumentation into indy-other

SylvainJuge · SylvainJuge · commit d9c04c3cd974 · 2025-10-30T18:33:08.000+01:00
diff --git a/docs/instrumentation-list.yaml b/docs/instrumentation-list.yaml
@@ -5300,8 +5300,12 @@ libraries:
   - name: jaxrs-1.0
     display_name: JAX-RS 1.x
     description: |
-      This instrumentation enables spans for JAX-RS methods, and enriches existing HTTP server spans with route information.
+      This instrumentation enriches HTTP server spans with route information and enables controller spans for JAX-RS annotated methods (controller spans are disabled by default).
     library_link: https://javaee.github.io/javaee-spec/javadocs/javax/ws/rs/package-summary.html
+    disabled_by_default: true
+    features:
+    - HTTP_ROUTE
+    - CONTROLLER_SPANS
     source_path: instrumentation/jaxrs/jaxrs-1.0
     scope:
       name: io.opentelemetry.jaxrs-1.0
@@ -5325,8 +5329,12 @@ libraries:
   - name: jaxrs-2.0-annotations
     display_name: JAX-RS 2.x
     description: |
-      This instrumentation enables spans for JAX-RS annotated methods, and enriches existing HTTP server spans with route information.
+      This instrumentation enriches HTTP server spans with route information, and enables controller spans for JAX-RS annotated methods (controller spans are disabled by default).
     library_link: https://javaee.github.io/javaee-spec/javadocs/javax/ws/rs/package-summary.html
+    disabled_by_default: true
+    features:
+    - HTTP_ROUTE
+    - CONTROLLER_SPANS
     source_path: instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-annotations
     scope:
       name: io.opentelemetry.jaxrs-2.0-annotations
@@ -5354,8 +5362,11 @@ libraries:
   - name: jaxrs-2.0-cxf-3.2
     display_name: Apache CXF JAX-RS 2.x
     description: |
-      This instrumentation enables spans for JAX-RS methods when using Apache CXF, and enriches existing HTTP server spans with route information.
+      This instrumentation enriches HTTP server spans with route information, and enables controller spans for JAX-RS methods when using Apache CXF (controller spans are disabled by default).
     library_link: https://cxf.apache.org/
+    features:
+    - HTTP_ROUTE
+    - CONTROLLER_SPANS
     source_path: instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-cxf-3.2
     scope:
       name: io.opentelemetry.jaxrs-2.0-cxf-3.2
@@ -5394,8 +5405,11 @@ libraries:
   - name: jaxrs-2.0-jersey-2.0
     display_name: Eclipse Jersey JAX-RS 2.x
     description: |
-      This instrumentation enables spans for JAX-RS methods when using Jersey, and enriches existing HTTP server spans with route information.
+      This instrumentation enriches HTTP server spans with route information, and enables controller spans for JAX-RS methods when using Jersey (controller spans are disabled by default).
     library_link: https://eclipse-ee4j.github.io/jersey/
+    features:
+    - HTTP_ROUTE
+    - CONTROLLER_SPANS
     source_path: instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-jersey-2.0
     scope:
       name: io.opentelemetry.jaxrs-2.0-jersey-2.0
@@ -5434,8 +5448,11 @@ libraries:
   - name: jaxrs-2.0-resteasy-3.0
     display_name: JBoss RESTEasy JAX-RS 2.x
     description: |
-      This instrumentation enables spans for JAX-RS methods when using RESTEasy, and enriches existing HTTP server spans with route information.
+      This instrumentation enriches HTTP server spans with route information, and enables controller spans for JAX-RS methods when using RESTEasy (controller spans are disabled by default).
     library_link: https://resteasy.dev/
+    features:
+    - HTTP_ROUTE
+    - CONTROLLER_SPANS
     source_path: instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-resteasy-3.0
     scope:
       name: io.opentelemetry.jaxrs-2.0-resteasy-3.0
@@ -5474,8 +5491,11 @@ libraries:
   - name: jaxrs-2.0-resteasy-3.1
     display_name: JBoss RESTEasy JAX-RS 2.x
     description: |
-      This instrumentation enables spans for JAX-RS methods when using RESTEasy, and enriches existing HTTP server spans with route information.
+      This instrumentation enriches HTTP server spans with route information, and enables controller spans for JAX-RS methods when using RESTEasy (controller spans are disabled by default).
     library_link: https://resteasy.dev/
+    features:
+    - HTTP_ROUTE
+    - CONTROLLER_SPANS
     source_path: instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-resteasy-3.1
     scope:
       name: io.opentelemetry.jaxrs-2.0-resteasy-3.1
@@ -5514,8 +5534,12 @@ libraries:
   - name: jaxrs-3.0-annotations
     display_name: JAX-RS 3.x
     description: |
-      This instrumentation enables spans for JAX-RS annotated methods, and enriches existing HTTP server spans with route information.
+      This instrumentation enriches HTTP server spans with route information, and enables controller spans for JAX-RS annotated methods (controller spans are disabled by default).
     library_link: https://jakarta.ee/specifications/restful-ws/3.0/
+    disabled_by_default: true
+    features:
+    - HTTP_ROUTE
+    - CONTROLLER_SPANS
     source_path: instrumentation/jaxrs/jaxrs-3.0/jaxrs-3.0-annotations
     scope:
       name: io.opentelemetry.jaxrs-3.0-annotations
@@ -5543,8 +5567,11 @@ libraries:
   - name: jaxrs-3.0-jersey-3.0
     display_name: Eclipse Jersey JAX-RS 3.x
     description: |
-      This instrumentation enables spans for JAX-RS methods when using Jersey, and enriches existing HTTP server spans with route information.
+      This instrumentation enriches HTTP server spans with route information, and enables controller spans for JAX-RS methods when using Jersey (controller spans are disabled by default).
     library_link: https://eclipse-ee4j.github.io/jersey/
+    features:
+    - HTTP_ROUTE
+    - CONTROLLER_SPANS
     source_path: instrumentation/jaxrs/jaxrs-3.0/jaxrs-3.0-jersey-3.0
     minimum_java_version: 11
     scope:
@@ -5583,8 +5610,11 @@ libraries:
   - name: jaxrs-3.0-resteasy-6.0
     display_name: JBoss RESTEasy JAX-RS 3.x
     description: |
-      This instrumentation enables spans for JAX-RS methods when using RESTEasy, and enriches existing HTTP server spans with route information.
+      This instrumentation enriches HTTP server spans with route information, and enables controller spans for JAX-RS methods when using RESTEasy (controller spans are disabled by default).
     library_link: https://resteasy.dev/
+    features:
+    - HTTP_ROUTE
+    - CONTROLLER_SPANS
     source_path: instrumentation/jaxrs/jaxrs-3.0/jaxrs-3.0-resteasy-6.0
     minimum_java_version: 11
     scope:
diff --git a/instrumentation/jaxrs/jaxrs-1.0/metadata.yaml b/instrumentation/jaxrs/jaxrs-1.0/metadata.yaml
@@ -1,7 +1,11 @@
 display_name: JAX-RS 1.x
 description: >
-  This instrumentation enables spans for JAX-RS methods, and enriches existing HTTP server spans
-  with route information.
+  This instrumentation enriches HTTP server spans with route information and enables controller
+  spans for JAX-RS annotated methods (controller spans are disabled by default).
+features:
+  - HTTP_ROUTE
+  - CONTROLLER_SPANS
+disabled_by_default: true
 library_link: https://javaee.github.io/javaee-spec/javadocs/javax/ws/rs/package-summary.html
 configurations:
   - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
diff --git a/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-annotations/metadata.yaml b/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-annotations/metadata.yaml
@@ -1,8 +1,12 @@
 display_name: JAX-RS 2.x
 description: >
-  This instrumentation enables spans for JAX-RS annotated methods, and enriches existing HTTP server
-  spans with route information.
+  This instrumentation enriches HTTP server spans with route information, and enables controller
+  spans for JAX-RS annotated methods (controller spans are disabled by default).
 library_link: https://javaee.github.io/javaee-spec/javadocs/javax/ws/rs/package-summary.html
+features:
+  - HTTP_ROUTE
+  - CONTROLLER_SPANS
+disabled_by_default: true
 configurations:
   - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
     description: Enables the creation of experimental controller spans.
diff --git a/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-cxf-3.2/metadata.yaml b/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-cxf-3.2/metadata.yaml
@@ -1,8 +1,11 @@
 display_name: Apache CXF JAX-RS 2.x
 description: >
-  This instrumentation enables spans for JAX-RS methods when using Apache CXF, and enriches
-  existing HTTP server spans with route information.
+  This instrumentation enriches HTTP server spans with route information, and enables controller
+  spans for JAX-RS methods when using Apache CXF (controller spans are disabled by default).
 library_link: https://cxf.apache.org/
+features:
+  - HTTP_ROUTE
+  - CONTROLLER_SPANS
 configurations:
   - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
     description: Enables the creation of experimental controller spans.
diff --git a/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-jersey-2.0/metadata.yaml b/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-jersey-2.0/metadata.yaml
@@ -1,8 +1,11 @@
 display_name: Eclipse Jersey JAX-RS 2.x
 description: >
-  This instrumentation enables spans for JAX-RS methods when using Jersey, and enriches
-  existing HTTP server spans with route information.
+  This instrumentation enriches HTTP server spans with route information, and enables controller
+  spans for JAX-RS methods when using Jersey (controller spans are disabled by default).
 library_link: https://eclipse-ee4j.github.io/jersey/
+features:
+  - HTTP_ROUTE
+  - CONTROLLER_SPANS
 configurations:
   - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
     description: Enables the creation of experimental controller spans.
diff --git a/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-resteasy-3.0/metadata.yaml b/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-resteasy-3.0/metadata.yaml
@@ -1,8 +1,11 @@
 display_name: JBoss RESTEasy JAX-RS 2.x
 description: >
-  This instrumentation enables spans for JAX-RS methods when using RESTEasy, and enriches existing
-  HTTP server spans with route information.
+  This instrumentation enriches HTTP server spans with route information, and enables controller
+  spans for JAX-RS methods when using RESTEasy (controller spans are disabled by default).
 library_link: https://resteasy.dev/
+features:
+  - HTTP_ROUTE
+  - CONTROLLER_SPANS
 configurations:
   - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
     description: Enables the creation of experimental controller spans.
diff --git a/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-resteasy-3.1/metadata.yaml b/instrumentation/jaxrs/jaxrs-2.0/jaxrs-2.0-resteasy-3.1/metadata.yaml
@@ -1,8 +1,11 @@
 display_name: JBoss RESTEasy JAX-RS 2.x
 description: >
-  This instrumentation enables spans for JAX-RS methods when using RESTEasy, and enriches existing
-  HTTP server spans with route information.
+  This instrumentation enriches HTTP server spans with route information, and enables controller
+  spans for JAX-RS methods when using RESTEasy (controller spans are disabled by default).
 library_link: https://resteasy.dev/
+features:
+  - HTTP_ROUTE
+  - CONTROLLER_SPANS
 configurations:
   - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
     description: Enables the creation of experimental controller spans.
diff --git a/instrumentation/jaxrs/jaxrs-3.0/jaxrs-3.0-annotations/metadata.yaml b/instrumentation/jaxrs/jaxrs-3.0/jaxrs-3.0-annotations/metadata.yaml
@@ -1,8 +1,12 @@
 display_name: JAX-RS 3.x
 description: >
-  This instrumentation enables spans for JAX-RS annotated methods, and enriches existing HTTP server
-  spans with route information.
+  This instrumentation enriches HTTP server spans with route information, and enables controller
+  spans for JAX-RS annotated methods (controller spans are disabled by default).
 library_link: https://jakarta.ee/specifications/restful-ws/3.0/
+features:
+  - HTTP_ROUTE
+  - CONTROLLER_SPANS
+disabled_by_default: true
 configurations:
   - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
     description: Enables the creation of experimental controller spans.
diff --git a/instrumentation/jaxrs/jaxrs-3.0/jaxrs-3.0-jersey-3.0/metadata.yaml b/instrumentation/jaxrs/jaxrs-3.0/jaxrs-3.0-jersey-3.0/metadata.yaml
@@ -1,8 +1,11 @@
 display_name: Eclipse Jersey JAX-RS 3.x
 description: >
-  This instrumentation enables spans for JAX-RS methods when using Jersey, and enriches existing
-  HTTP server spans with route information.
+  This instrumentation enriches HTTP server spans with route information, and enables controller
+  spans for JAX-RS methods when using Jersey (controller spans are disabled by default).
 library_link: https://eclipse-ee4j.github.io/jersey/
+features:
+  - HTTP_ROUTE
+  - CONTROLLER_SPANS
 configurations:
   - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
     description: Enables the creation of experimental controller spans.
diff --git a/instrumentation/jaxrs/jaxrs-3.0/jaxrs-3.0-resteasy-6.0/metadata.yaml b/instrumentation/jaxrs/jaxrs-3.0/jaxrs-3.0-resteasy-6.0/metadata.yaml
@@ -1,8 +1,11 @@
 display_name: JBoss RESTEasy JAX-RS 3.x
 description: >
-  This instrumentation enables spans for JAX-RS methods when using RESTEasy, and enriches existing
-  HTTP server spans with route information.
+  This instrumentation enriches HTTP server spans with route information, and enables controller
+  spans for JAX-RS methods when using RESTEasy (controller spans are disabled by default).
 library_link: https://resteasy.dev/
+features:
+  - HTTP_ROUTE
+  - CONTROLLER_SPANS
 configurations:
   - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
     description: Enables the creation of experimental controller spans.
diff --git a/instrumentation/jmx-metrics/README.md b/instrumentation/jmx-metrics/README.md
@@ -229,6 +229,10 @@ The metric descriptions will remain undefined, unless they are provided by the q
 ### State Metrics
 
 Some JMX attributes expose current state as a non-numeric MBean attribute, in order to capture those as metrics it is recommended to use the special `state` metric type.
+
+This type of metric fits the [semantic conventions recommendations for state metric](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/how-to-write-conventions/status-metrics.md),
+using the `.status` suffix is compliant with the [naming recommendations](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/how-to-write-conventions/status-metrics.md#naming).
+
 For example, with Tomcat connector, the `Catalina:type=Connector,port=*` MBean has `stateName` (of type `String`), we can define the following rule:
 
 ```yaml
@@ -238,56 +242,56 @@ rules:
     mapping:
       stateName:
         type: state
-        metric: tomcat.connector
+        metric: tomcat.connector.status
         metricAttribute:
           port: param(port)
-          connector_state:
+          tomcat.connector.state:
             ok: STARTED
             failed: [STOPPED,FAILED]
             degraded: '*'
 ```
 
-For a given value of `port`, let's say `8080` This will capture the `tomcat.connector.state` metric of type `updowncounter` with value `0` or `1` and the `state` metric attribute will have a value in [`ok`,`failed`,`degraded`].
-For every sample, 3 metrics will be captured for each value of `state` depending on the value of `stateName`:
+For a given value of `port`, let's say `8080` This will capture the `tomcat.connector.status` metric of type `updowncounter` with value `0` or `1` and the `tomcat.connector.state` metric attribute will have a value in [`ok`,`failed`,`degraded`].
+For every sample, 3 metrics will be captured for each value of `tomcat.connector.state` depending on the value of `stateName`:
 
 When `stateName` = `STARTED`, we have:
 
-- `tomcat.connector` value = `1`, attributes `port` = `8080` and `connector_state` = `ok`
-- `tomcat.connector` value = `0`, attributes `port` = `8080` and `connector_state` = `failed`
-- `tomcat.connector` value = `0`, attributes `port` = `8080` and `connector_state` = `degraded`
+- `tomcat.connector.status` value = `1`, attributes `port` = `8080` and `tomcat.connector.state` = `ok`
+- `tomcat.connector.status` value = `0`, attributes `port` = `8080` and `tomcat.connector.state` = `failed`
+- `tomcat.connector.status` value = `0`, attributes `port` = `8080` and `tomcat.connector.state` = `degraded`
 
 When `stateName` = `STOPPED` or `FAILED`, we have:
 
-- `tomcat.connector` value = `0`, attributes `port` = `8080` and `connector_state` = `ok`
-- `tomcat.connector` value = `1`, attributes `port` = `8080` and `connector_state` = `failed`
-- `tomcat.connector` value = `0`, attributes `port` = `8080` and `connector_state` = `degraded`
+- `tomcat.connector.status` value = `0`, attributes `port` = `8080` and `tomcat.connector.state` = `ok`
+- `tomcat.connector.status` value = `1`, attributes `port` = `8080` and `tomcat.connector.state` = `failed`
+- `tomcat.connector.status` value = `0`, attributes `port` = `8080` and `tomcat.connector.state` = `degraded`
 
 For other values of `stateName`, we have:
 
-- `tomcat.connector` value = `0`, attributes `port` = `8080` and `connector_state` = `ok`
-- `tomcat.connector` value = `0`, attributes `port` = `8080` and `connector_state` = `failed`
-- `tomcat.connector` value = `1`, attributes `port` = `8080` and `connector_state` = `degraded`
+- `tomcat.connector.status` value = `0`, attributes `port` = `8080` and `tomcat.connector.state` = `ok`
+- `tomcat.connector.status` value = `0`, attributes `port` = `8080` and `tomcat.connector.state` = `failed`
+- `tomcat.connector.status` value = `1`, attributes `port` = `8080` and `tomcat.connector.state` = `degraded`
 
 Each state key can be mapped to one or more values of the MBean attribute using:
 - a string literal or a string array
 - a `*` character to provide default option and avoid enumerating all values, this value must be quoted in YAML
 
 Exactly one `*` value must be present in the mapping to ensure all possible values of the MBean attribute can be mapped to a state key.
 
-The default value indicated by `*` does not require a dedicated state key. For example, if we want to have `connector_state` metric attribute with values `on` or `off`, we can use:
+The default value indicated by `*` does not require a dedicated state key. For example, if we want to have `tomcat.connector.state` metric attribute with values `on` or `off`, we can use:
 ```yaml
-          connector_state:
+          tomcat.connector.state:
             on: STARTED
             off: [STOPPED,FAILED,'*']
 ```
 In the particular case where only two values are defined, we can simplify further by explicitly defining one state and rely on default for the other.
 ```yaml
-          connector_state:
+          tomcat.connector.state:
             on: STARTED
             off: '*'
 ```
 
-State metrics do not have a unit (nor source unit) and use an empty string `""` as unit.
+State metrics do not need to define `unit` nor `sourceUnit` attributes, the unit of the metric will always be `1`.
 
 ### Metric attributes modifiers
 
diff --git a/instrumentation/jmx-metrics/library/src/main/java/io/opentelemetry/instrumentation/jmx/yaml/JmxRule.java b/instrumentation/jmx-metrics/library/src/main/java/io/opentelemetry/instrumentation/jmx/yaml/JmxRule.java
@@ -207,7 +207,7 @@ private static List<MetricExtractor> createStateMappingExtractors(
               metricInfo.getMetricName(),
               metricInfo.getDescription(),
               null,
-              "",
+              "1",
               MetricInfo.Type.UPDOWNCOUNTER);
 
       extractors.add(new MetricExtractor(extractor, stateMetricInfo, stateMetricAttributes));
diff --git a/instrumentation/jmx-metrics/library/src/test/java/io/opentelemetry/instrumentation/jmx/engine/RuleParserTest.java b/instrumentation/jmx-metrics/library/src/test/java/io/opentelemetry/instrumentation/jmx/engine/RuleParserTest.java
@@ -453,8 +453,8 @@ void testStateMetricConf() throws Exception {
               assertThat(me.getInfo().getMetricName()).isEqualTo("state_metric");
               assertThat(me.getInfo().getType()).isEqualTo(MetricInfo.Type.UPDOWNCOUNTER);
               assertThat(me.getInfo().getUnit())
-                  .describedAs("state metric unit should be an empty string")
-                  .isEmpty();
+                  .describedAs("state metric unit should be 1")
+                  .isEqualTo("1");
 
               assertThat(me.getAttributes()).hasSize(1);
               MetricAttribute stateAttribute = me.getAttributes().get(0);
diff --git a/instrumentation/jmx-metrics/library/src/test/java/io/opentelemetry/instrumentation/jmx/yaml/MetricStructureTest.java b/instrumentation/jmx-metrics/library/src/test/java/io/opentelemetry/instrumentation/jmx/yaml/MetricStructureTest.java
@@ -80,7 +80,7 @@ void metricAttribute_beanParam(String target, String value, String expectedValue
         "param()", // missing parameter
         "param( )", // missing parameter with empty string
         "param(name)a", // something after parenthesis
-        "lowercase()", // misng target in modifier
+        "lowercase()", // missing target in modifier
         "lowercase(param(name)", // missing parenthesis for modifier
         "lowercase(missing(name))", // non-existing target within modifier
         "lowercase(param())", // missing parameter in modifier
diff --git a/instrumentation/lettuce/lettuce-5.1/testing/src/main/java/io/opentelemetry/instrumentation/lettuce/v5_1/AbstractLettuceAsyncClientTest.java b/instrumentation/lettuce/lettuce-5.1/testing/src/main/java/io/opentelemetry/instrumentation/lettuce/v5_1/AbstractLettuceAsyncClientTest.java
@@ -147,7 +147,8 @@ void testConnectExceptionInsideTheConnectionFuture() {
 
   @Test
   void testSetCommandUsingFutureGetWithTimeout() throws Exception {
-    RedisFuture<String> redisFuture = asyncCommands.set("TESTSETKEY", "TESTSETVAL");
+    RedisFuture<String> redisFuture =
+        testing().runWithSpan("parent", () -> asyncCommands.set("TESTSETKEY", "TESTSETVAL"));
     String res = redisFuture.get(3, TimeUnit.SECONDS);
 
     assertThat(res).isEqualTo("OK");
@@ -156,9 +157,11 @@ void testSetCommandUsingFutureGetWithTimeout() throws Exception {
         .waitAndAssertTraces(
             trace ->
                 trace.hasSpansSatisfyingExactly(
+                    span -> span.hasName("parent").hasKind(SpanKind.INTERNAL).hasNoParent(),
                     span ->
                         span.hasName("SET")
                             .hasKind(SpanKind.CLIENT)
+                            .hasParent(trace.getSpan(0))
                             .hasAttributesSatisfyingExactly(
                                 addExtraAttributes(
                                     equalTo(NETWORK_TYPE, "ipv4"),
diff --git a/instrumentation/lettuce/lettuce-5.1/testing/src/main/java/io/opentelemetry/instrumentation/lettuce/v5_1/AbstractLettuceReactiveClientTest.java b/instrumentation/lettuce/lettuce-5.1/testing/src/main/java/io/opentelemetry/instrumentation/lettuce/v5_1/AbstractLettuceReactiveClientTest.java
diff --git a/instrumentation/lettuce/lettuce-5.1/testing/src/main/java/io/opentelemetry/instrumentation/lettuce/v5_1/AbstractLettuceSyncClientTest.java b/instrumentation/lettuce/lettuce-5.1/testing/src/main/java/io/opentelemetry/instrumentation/lettuce/v5_1/AbstractLettuceSyncClientTest.java
diff --git a/instrumentation/openai/openai-java-1.1/testing/src/main/java/io/opentelemetry/instrumentation/openai/v1_1/AbstractChatTest.java b/instrumentation/openai/openai-java-1.1/testing/src/main/java/io/opentelemetry/instrumentation/openai/v1_1/AbstractChatTest.java
