Another batch of metadata updates

docs/instrumentation-list.yaml

@@ -2099,7 +2099,20 @@ libraries:
       name: io.opentelemetry.azure-core-1.36
     target_versions:
       javaagent:
-      - com.azure:azure-core:[1.36.0,)
+      - com.azure:azure-core:[1.36.0,1.53.0)
+  - name: azure-core-1.53
+    description: This instrumentation enables context propagation for the Azure Core
+      library, it does not emit any telemetry on its own.
+    library_link: https://learn.microsoft.com/en-us/java/api/overview/azure/core-readme?view=azure-java-stable
+    features:
+    - CONTEXT_PROPAGATION
+    - AUTO_INSTRUMENTATION_SHIM
+    source_path: instrumentation/azure-core/azure-core-1.53
+    scope:
+      name: io.opentelemetry.azure-core-1.53
+    target_versions:
+      javaagent:
+      - com.azure:azure-core:[1.53.0,)
   c3p0:
   - name: c3p0-0.9
     description: The c3p0 instrumentation provides connection pool metrics for c3p0
@@ -3722,9 +3735,12 @@ libraries:
           type: STRING
   executors:
   - name: executors
+    display_name: Java Executors
     description: |
       The executor instrumentation ensures that context is automatically propagated when using common Java executors (e.g., ThreadPoolExecutor, ScheduledThreadPoolExecutor, ForkJoinPool). When a task is submitted, the current context is captured and bound to the task. Then, when the task eventually runs, even if it’s on a different thread, the instrumentation reactivates that context, enabling consistent correlation across concurrent and asynchronous workflows.
     library_link: https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/Executor.html
+    features:
+    - CONTEXT_PROPAGATION
     source_path: instrumentation/executors
     scope:
       name: io.opentelemetry.executors
@@ -3777,6 +3793,8 @@ libraries:
     description: |
       This instrumentation for Finagle HTTP clients and servers ensures that telemetry is correctly generated by the underlying Netty instrumentation. It augments existing telemetry by bridging the gap between Finagle's abstractions and Netty's pipeline, primarily for context propagation.
     library_link: https://github.com/twitter/finagle
+    features:
+    - CONTEXT_PROPAGATION
     source_path: instrumentation/finagle-http-23.11
     scope:
       name: io.opentelemetry.finagle-http-23.11
@@ -3810,6 +3828,9 @@ libraries:
   - name: geode-1.4
     description: This instrumentation enables database client spans and database client
       metrics for Apache Geode cache operations.
+    semantic_conventions:
+    - DATABASE_CLIENT_SPANS
+    - DATABASE_CLIENT_METRICS
     library_link: https://geode.apache.org/
     source_path: instrumentation/geode-1.4
     scope:
@@ -9222,6 +9243,17 @@ custom:
   target_versions:
     javaagent:
     - Java 8+
+  configurations:
+  - name: otel.instrumentation.external-annotations.include
+    description: Configuration for trace annotations, in the form of a pattern that
+      matches `'package.Annotation$Name;*'`.
+    type: string
+    default: ''
+  - name: otel.instrumentation.external-annotations.exclude-methods
+    description: All methods to be excluded from auto-instrumentation by annotation-based
+      advices.
+    type: string
+    default: ''
 - name: opentelemetry-extension-annotations-1.0
   description: |
     Instruments methods annotated with OpenTelemetry extension annotations, such as @WithSpan and @SpanAttribute.

instrumentation/executors/metadata.yaml

@@ -1,10 +1,13 @@
+display_name: Java Executors
 description: >
   The executor instrumentation ensures that context is automatically propagated when using common
   Java executors (e.g., ThreadPoolExecutor, ScheduledThreadPoolExecutor, ForkJoinPool). When a task
   is submitted, the current context is captured and bound to the task. Then, when the task
   eventually runs, even if it’s on a different thread, the instrumentation reactivates that context,
   enabling consistent correlation across concurrent and asynchronous workflows.
 library_link: https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/Executor.html
+features:
+- CONTEXT_PROPAGATION
 configurations:
   - name: otel.instrumentation.executors.include
     description: List of Executor subclasses to be instrumented.

instrumentation/external-annotations/metadata.yaml

@@ -7,3 +7,13 @@ description: >
   appropriate OpenTelemetry instrumentation logic, including span creation and context propagation.
   Covers many common vendor annotations by default, and additional annotations can be targeted using
   the configuration property "otel.instrumentation.external-annotations.include".
+configurations:
+  - name: otel.instrumentation.external-annotations.include
+    description: Configuration for trace annotations, in the form of a pattern that matches
+      `'package.Annotation$Name;*'`.
+    type: string
+    default: ""
+  - name: otel.instrumentation.external-annotations.exclude-methods
+    description: All methods to be excluded from auto-instrumentation by annotation-based advices.
+    type: string
+    default: ""

instrumentation/finagle-http-23.11/metadata.yaml

@@ -3,3 +3,5 @@ description: >
   generated by the underlying Netty instrumentation. It augments existing telemetry by bridging the
   gap between Finagle's abstractions and Netty's pipeline, primarily for context propagation.
 library_link: https://github.com/twitter/finagle
+features:
+  - CONTEXT_PROPAGATION

instrumentation/geode-1.4/metadata.yaml

@@ -1,5 +1,8 @@
 description: This instrumentation enables database client spans and database client metrics for Apache Geode cache operations.
 library_link: https://geode.apache.org/
+semantic_conventions:
+  - DATABASE_CLIENT_SPANS
+  - DATABASE_CLIENT_METRICS
 configurations:
   - name: otel.instrumentation.common.db-statement-sanitizer.enabled
     description: Enables statement sanitization for database queries.