Add links to remaining metadata files (#14633)

2025-09-11 14:27:43 -04:00 · 2025-09-11 14:27:43 -04:00 · b444563cfe
parent bf7c9645f6
commit b444563cfe
58 changed files with 111 additions and 2 deletions
--- a/docs/instrumentation-list.yaml
+++ b/docs/instrumentation-list.yaml
@ -2983,6 +2983,7 @@ libraries:
  - name: 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
    source_path: instrumentation/executors
    scope:
      name: io.opentelemetry.executors
@ -3002,6 +3003,7 @@ libraries:
  - name: finagle-http-23.11
    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
    source_path: instrumentation/finagle-http-23.11
    scope:
      name: io.opentelemetry.finagle-http-23.11
@ -3014,6 +3016,7 @@ libraries:
    description: This instrumentation for the Finatra web framework augments the telemetry
      generated by the underlying Netty instrumentation. It provides more specific,
      high-level context, such as route information, to the spans generated by Netty.
+    library_link: https://github.com/twitter/finatra
    source_path: instrumentation/finatra-2.9
    scope:
      name: io.opentelemetry.finatra-2.9
@ -3034,6 +3037,7 @@ libraries:
  - name: geode-1.4
    description: This instrumentation enables database client spans and database client
      metrics for Apache Geode cache operations.
+    library_link: https://geode.apache.org/
    source_path: instrumentation/geode-1.4
    scope:
      name: io.opentelemetry.geode-1.4
@ -3156,6 +3160,7 @@ libraries:
  - name: grails-3.0
    description: |
      This instrumentation enriches existing HTTP server spans with HTTP route information, and optionally enables experimental controller (INTERNAL) spans for Grails applications.
+    library_link: https://grails.apache.org/
    source_path: instrumentation/grails-3.0
    scope:
      name: io.opentelemetry.grails-3.0
@ -3208,6 +3213,7 @@ libraries:
          type: STRING
  - name: graphql-java-20.0
    description: This instrumentation enables spans for GraphQL Java operations.
+    library_link: https://www.graphql-java.com/
    source_path: instrumentation/graphql-java/graphql-java-20.0
    minimum_java_version: 11
    scope:
@ -3266,6 +3272,7 @@ libraries:
  - name: grizzly-2.3
    description: This instrumentation enables HTTP server spans and HTTP server metrics
      for Grizzly applications.
+    library_link: https://javaee.github.io/grizzly/httpserverframework.html
    source_path: instrumentation/grizzly-2.3
    scope:
      name: io.opentelemetry.grizzly-2.3
@ -3347,6 +3354,7 @@ libraries:
  - name: grpc-1.6
    description: This instrumentation enables RPC client spans and metrics, and RPC
      server spans and metrics for gRPC version 1.6 and above.
+    library_link: https://github.com/grpc/grpc-java
    source_path: instrumentation/grpc-1.6
    scope:
      name: io.opentelemetry.grpc-1.6
@ -3544,6 +3552,7 @@ libraries:
  gwt:
  - name: gwt-2.0
    description: This instrumentation enables RPC server spans for GWT RPC requests.
+    library_link: https://www.gwtproject.org/
    source_path: instrumentation/gwt-2.0
    scope:
      name: io.opentelemetry.gwt-2.0
@ -3566,6 +3575,7 @@ libraries:
  - name: hibernate-3.3
    description: |
      This instrumentation enables the generation of INTERNAL spans for Hibernate operations, including session methods (e.g., `save`, `update`, `delete`), transaction commits, and query executions.
+    library_link: https://github.com/hibernate/hibernate-orm
    source_path: instrumentation/hibernate/hibernate-3.3
    scope:
      name: io.opentelemetry.hibernate-3.3
@ -3592,6 +3602,7 @@ libraries:
  - name: hibernate-4.0
    description: |
      This instrumentation enables the generation of INTERNAL spans for Hibernate operations, including session methods (e.g., `save`, `update`, `delete`), transaction commits, and query executions.
+    library_link: https://github.com/hibernate/hibernate-orm
    source_path: instrumentation/hibernate/hibernate-4.0
    scope:
      name: io.opentelemetry.hibernate-4.0
@ -3618,6 +3629,7 @@ libraries:
  - name: hibernate-6.0
    description: |
      This instrumentation enables the generation of INTERNAL spans for Hibernate operations, including session methods (e.g., `save`, `update`, `delete`), transaction commits, and query executions.
+    library_link: https://github.com/hibernate/hibernate-orm
    source_path: instrumentation/hibernate/hibernate-6.0
    minimum_java_version: 11
    scope:
@ -3645,6 +3657,7 @@ libraries:
  - name: hibernate-procedure-call-4.3
    description: This instrumentation enables the generation of INTERNAL spans for
      Hibernate stored procedure calls.
+    library_link: https://github.com/hibernate/hibernate-orm
    source_path: instrumentation/hibernate/hibernate-procedure-call-4.3
    scope:
      name: io.opentelemetry.hibernate-procedure-call-4.3
@ -3671,6 +3684,7 @@ libraries:
  - name: hibernate-reactive-1.0
    description: |
      This instrumentation does not emit any telemetry on its own. Instead, it enables context propagation for Hibernate Reactive asynchronous operations.
+    library_link: https://hibernate.org/reactive/
    source_path: instrumentation/hibernate/hibernate-reactive-1.0
    scope:
      name: io.opentelemetry.hibernate-reactive-1.0
@ -3681,6 +3695,7 @@ libraries:
  - name: hikaricp-3.0
    description: |
      This instrumentation provides database client metrics for HikariCP 3.0+ connection pools. It reports metrics like connection timeouts, creation time, wait time, and usage time, along with connection pool statistics such as the number of active, idle, and pending connections.
+    library_link: https://github.com/brettwooldridge/HikariCP
    source_path: instrumentation/hikaricp-3.0
    scope:
      name: io.opentelemetry.hikaricp-3.0
@ -3821,6 +3836,7 @@ libraries:
  - name: http-url-connection
    description: |
      This instrumentation enables the generation of HTTP client spans and HTTP client metrics for requests made using `java.net.HttpURLConnection`.
+    library_link: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/net/HttpURLConnection.html
    source_path: instrumentation/http-url-connection
    scope:
      name: io.opentelemetry.http-url-connection
@ -3894,6 +3910,7 @@ libraries:
  - name: hystrix-1.4
    description: This instrumentation enables the generation of INTERNAL spans for
      Hystrix command executions and fallbacks.
+    library_link: https://github.com/Netflix/Hystrix
    source_path: instrumentation/hystrix-1.4
    scope:
      name: io.opentelemetry.hystrix-1.4
@ -3925,6 +3942,7 @@ libraries:
  - name: influxdb-2.4
    description: This instrumentation enables the generation of database client spans
      and metrics for the InfluxDB Java client.
+    library_link: https://github.com/influxdata/influxdb-java
    source_path: instrumentation/influxdb-2.4
    scope:
      name: io.opentelemetry.influxdb-2.4
@ -3984,6 +4002,7 @@ libraries:
  - name: java-http-client
    description: This instrumentation enables HTTP client spans and HTTP client metrics
      for requests made using the Java HTTP client.
+    library_link: https://docs.oracle.com/en/java/javase/11/docs/api/java.net.http/java/net/http/package-summary.html
    source_path: instrumentation/java-http-client
    minimum_java_version: 11
    scope:
@ -4059,6 +4078,7 @@ libraries:
  - name: java-http-server
    description: This instrumentation enables HTTP server spans and HTTP server metrics
      for the Java HTTP server.
+    library_link: https://docs.oracle.com/en/java/javase/21/docs/api/jdk.httpserver/module-summary.html
    source_path: instrumentation/java-http-server
    scope:
      name: io.opentelemetry.java-http-server
@ -4142,6 +4162,7 @@ libraries:
  - name: javalin-5.0
    description: This instrumentation enriches existing HTTP server spans with route
      information, it does not emit any telemetry on its own.
+    library_link: https://javalin.io/
    source_path: instrumentation/javalin-5.0
    minimum_java_version: 11
    scope:
@ -4277,6 +4298,7 @@ libraries:
    description: |
      The JDBC instrumentation provides database client spans and metrics. Each call produces a span named after the SQL verb, enriched with standard DB client attributes (system, database, operation, sanitized statement, peer address) and error details if an exception occurs.
      There is also a "jdbc-datasource" instrumentation that creates spans for datasource connections, but is disabled by default due to the volume of telemetry produced.
+    library_link: https://docs.oracle.com/javase/8/docs/api/java/sql/package-summary.html
    source_path: instrumentation/jdbc
    scope:
      name: io.opentelemetry.jdbc
@ -4561,6 +4583,7 @@ libraries:
  - name: kafka-clients-0.11
    description: |
      This instrumentation enables messaging spans and metrics for Apache Kafka 0.11 clients. It automatically traces message production and consumption, propagates context, and emits metrics for production and consumption.
+    library_link: https://kafka.apache.org/
    source_path: instrumentation/kafka/kafka-clients/kafka-clients-0.11
    scope:
      name: io.opentelemetry.kafka-clients-0.11
@ -4588,6 +4611,7 @@ libraries:
  - name: kafka-clients-2.6
    description: |
      This instrumentation provides a library integration that enables messaging spans and metrics for Apache Kafka 2.6+ clients.
+    library_link: https://kafka.apache.org/
    source_path: instrumentation/kafka/kafka-clients/kafka-clients-2.6
    scope:
      name: io.opentelemetry.kafka-clients-2.6
@ -4605,6 +4629,7 @@ libraries:
      type: boolean
      default: false
  - name: kafka-streams-0.11
+    library_link: https://kafka.apache.org/documentation/streams/
    source_path: instrumentation/kafka/kafka-streams-0.11
    scope:
      name: io.opentelemetry.kafka-streams-0.11
@ -5208,6 +5233,7 @@ libraries:
  - name: openai-java-1.1
    description: This instrumentation enables Gen AI client spans and metrics for
      OpenAI Java SDK 1.1+.
+    library_link: https://github.com/openai/openai-java
    source_path: instrumentation/openai/openai-java-1.1
    scope:
      name: io.opentelemetry.openai-java-1.1
@ -5321,6 +5347,7 @@ libraries:
  - name: oracle-ucp-11.2
    description: The Oracle Universal Connection Pool (UCP) instrumentation generates
      connection pool metrics.
+    library_link: https://docs.oracle.com/database/121/JJUCP/
    source_path: instrumentation/oracle-ucp-11.2
    scope:
      name: io.opentelemetry.oracle-ucp-11.2
@ -5389,6 +5416,7 @@ libraries:
    description: When the OSHI library is detected on the classpath, this instrumentation
      will use the system class loader to load classes from the oshi-core jar that
      are then used to generate system metrics.
+    library_link: https://github.com/oshi/oshi/
    source_path: instrumentation/oshi
    scope:
      name: io.opentelemetry.oshi
@ -6107,6 +6135,7 @@ libraries:
  - name: spark-2.3
    description: |
      This instrumentation does not emit telemetry on its own. Instead, it extracts the HTTP route and attaches it to HTTP server spans and HTTP server metrics.
+    library_link: https://sparkjava.com/
    source_path: instrumentation/spark-2.3
    scope:
      name: io.opentelemetry.spark-2.3
@ -6117,6 +6146,7 @@ libraries:
  - name: spring-batch-3.0
    description: This instrumentation enables INTERNAL spans for jobs run by the Spring
      Batch framework.
+    library_link: https://spring.io/projects/spring-batch
    disabled_by_default: true
    source_path: instrumentation/spring/spring-batch-3.0
    scope:
@ -6149,6 +6179,7 @@ libraries:
  - name: spring-boot-actuator-autoconfigure-2.0
    description: |
      This instrumentation configures the OpenTelemetry Micrometer bridge to receive metrics from Spring Boot Actuator. It does not produce telemetry on its own.
+    library_link: https://spring.io/projects/spring-boot
    disabled_by_default: true
    source_path: instrumentation/spring/spring-boot-actuator-autoconfigure-2.0
    scope:
@ -6168,12 +6199,14 @@ libraries:
        - Check for application.yml in the current working dir
        - Check for --spring.application.name program argument (not jvm arg) via ProcessHandle
        - Check for --spring.application.name program argument via sun.java.command system property
+    library_link: https://spring.io/projects/spring-boot
    source_path: instrumentation/spring/spring-boot-resources
    scope:
      name: io.opentelemetry.spring-boot-resources
  - name: spring-cloud-aws-3.0
    description: |
      This instrumentation enhances tracing for Spring Cloud AWS. It augments the existing AWS SDK instrumentation by providing higher-level tracing for SQS operations, capturing details specific to Spring Cloud AWS SQS usage and linking them to the underlying AWS SDK traces.
+    library_link: https://spring.io/projects/spring-cloud-aws
    source_path: instrumentation/spring/spring-cloud-aws-3.0
    minimum_java_version: 17
    scope:
@ -6184,6 +6217,7 @@ libraries:
  - name: spring-cloud-gateway-2.0
    description: |
      This instrumentation enhances tracing for Spring Cloud Gateway. It does not generate new telemetry on its own, but rather enriches existing traces produced by other instrumentations like Netty and Spring WebFlux with Spring Cloud Gateway-specific attributes.
+    library_link: https://github.com/spring-cloud/spring-cloud-gateway
    source_path: instrumentation/spring/spring-cloud-gateway/spring-cloud-gateway-2.0
    scope:
      name: io.opentelemetry.spring-cloud-gateway-2.0
@ -6199,6 +6233,7 @@ libraries:
  - name: spring-core-2.0
    description: |
      This instrumentation ensures proper context propagation for asynchronous operations within Spring Core. It modifies how tasks are submitted and executed to ensure that spans created by other instrumentations are correctly linked across thread boundaries, rather than generating any new telemetry itself.
+    library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/core/package-summary.html
    source_path: instrumentation/spring/spring-core-2.0
    minimum_java_version: 17
    scope:
@ -6209,6 +6244,7 @@ libraries:
  - name: spring-data-1.8
    description: |
      This instrumentation enhances tracing for Spring Data operations. It works in conjunction with other instrumentations, such as JDBC, to provide additional context and details for database interactions initiated through Spring Data.
+    library_link: https://spring.io/projects/spring-data
    source_path: instrumentation/spring/spring-data/spring-data-1.8
    scope:
      name: io.opentelemetry.spring-data-1.8
@ -6228,6 +6264,7 @@ libraries:
  - name: spring-integration-4.1
    description: This instrumentation enables producer and consumer messaging spans
      for Spring Integration.
+    library_link: https://spring.io/projects/spring-integration
    source_path: instrumentation/spring/spring-integration-4.1
    scope:
      name: io.opentelemetry.spring-integration-4.1
@ -6270,6 +6307,7 @@ libraries:
  - name: spring-jms-2.0
    description: This instrumentation enables the generation of consumer messaging
      spans for Spring JMS.
+    library_link: https://docs.spring.io/spring-framework/reference/integration/jms.html
    source_path: instrumentation/spring/spring-jms/spring-jms-2.0
    scope:
      name: io.opentelemetry.spring-jms-2.0
@ -6302,6 +6340,7 @@ libraries:
  - name: spring-jms-6.0
    description: This instrumentation enables the generation of consumer messaging
      spans for Spring JMS.
+    library_link: https://docs.spring.io/spring-framework/reference/integration/jms.html
    source_path: instrumentation/spring/spring-jms/spring-jms-6.0
    minimum_java_version: 17
    scope:
@ -6335,6 +6374,7 @@ libraries:
  - name: spring-kafka-2.7
    description: This instrumentation enables consumer messaging spans for Spring
      Kafka listeners.
+    library_link: https://spring.io/projects/spring-kafka
    source_path: instrumentation/spring/spring-kafka-2.7
    scope:
      name: io.opentelemetry.spring-kafka-2.7
@ -6409,6 +6449,7 @@ libraries:
  - name: spring-pulsar-1.0
    description: This instrumentation enables consumer messaging spans for Spring
      Pulsar listeners.
+    library_link: https://spring.io/projects/spring-pulsar
    source_path: instrumentation/spring/spring-pulsar-1.0
    minimum_java_version: 17
    scope:
@ -6449,6 +6490,7 @@ libraries:
  - name: spring-rabbit-1.0
    description: This instrumentation enables consumer messaging spans for Spring
      RabbitMQ listeners.
+    library_link: https://spring.io/projects/spring-amqp
    source_path: instrumentation/spring/spring-rabbit-1.0
    scope:
      name: io.opentelemetry.spring-rabbit-1.0
@ -6476,6 +6518,7 @@ libraries:
  - name: spring-rmi-4.0
    description: This instrumentation enables RPC client and RPC server spans for
      Spring RMI applications.
+    library_link: https://docs.spring.io/spring-framework/docs/4.0.x/javadoc-api/org/springframework/remoting/rmi/package-summary.html
    source_path: instrumentation/spring/spring-rmi-4.0
    scope:
      name: io.opentelemetry.spring-rmi-4.0
@ -6503,6 +6546,7 @@ libraries:
          type: STRING
  - name: spring-scheduling-3.1
    description: This instrumentation enables tracing for Spring Scheduling tasks.
+    library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/scheduling/package-summary.html
    source_path: instrumentation/spring/spring-scheduling-3.1
    scope:
      name: io.opentelemetry.spring-scheduling-3.1
@ -6538,6 +6582,7 @@ libraries:
    description: |
      This instrumentation does not emit any telemetry on its own. Instead, it captures enduser attributes, and is only enabled when at least one of the `enduser` configurations is enabled.
      NOTE: The `enduser` attributes have been deprecated and will be removed in 3.0+ of the java agent.
+    library_link: https://spring.io/projects/spring-security
    source_path: instrumentation/spring/spring-security-config-6.0
    minimum_java_version: 17
    scope:
@ -6577,6 +6622,7 @@ libraries:
  - name: spring-web-3.1
    description: |
      This instrumentation provides a library integration that enables capturing HTTP client spans and metrics for Spring's RestTemplate. The agent integration enriches HTTP server spans and metrics with route information.
+    library_link: https://github.com/spring-projects/spring-framework
    source_path: instrumentation/spring/spring-web/spring-web-3.1
    scope:
      name: io.opentelemetry.spring-web-3.1
@ -6617,6 +6663,7 @@ libraries:
  - name: spring-web-6.0
    description: This instrumentation enriches HTTP server spans and metrics with
      route information.
+    library_link: https://github.com/spring-projects/spring-framework
    source_path: instrumentation/spring/spring-web/spring-web-6.0
    minimum_java_version: 17
    scope:
@ -6627,6 +6674,7 @@ libraries:
  - name: spring-webflux-5.0
    description: |
      This instrumentation enables HTTP client spans and metrics for Spring WebFlux 5.0. It also optionally enables experimental controller (INTERNAL) spans.
+    library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/reactive/package-summary.html
    source_path: instrumentation/spring/spring-webflux/spring-webflux-5.0
    scope:
      name: io.opentelemetry.spring-webflux-5.0
@ -6680,6 +6728,7 @@ libraries:
  - name: spring-webflux-5.3
    description: |
      This instrumentation provides a library integration for the Spring WebFlux WebClient and Webflux server versions 5.3+ that enables HTTP client and server spans and metrics.
+    library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/reactive/package-summary.html
    source_path: instrumentation/spring/spring-webflux/spring-webflux-5.3
    scope:
      name: io.opentelemetry.spring-webflux-5.3
@ -6761,6 +6810,7 @@ libraries:
  - name: spring-webmvc-3.1
    description: |
      This instrumentation enables optional Controller and View (INTERNAL) spans for Spring WebMVC 3.1+.
+    library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/servlet/mvc/package-summary.html
    source_path: instrumentation/spring/spring-webmvc/spring-webmvc-3.1
    scope:
      name: io.opentelemetry.spring-webmvc-3.1
@ -6803,6 +6853,7 @@ libraries:
  - name: spring-webmvc-5.3
    description: |
      This instrumentation provides a library integration for Spring WebMVC controllers, that enables the creation of HTTP server spans and metrics for requests processed by the Spring servlet container.
+    library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/servlet/mvc/package-summary.html
    source_path: instrumentation/spring/spring-webmvc/spring-webmvc-5.3
    scope:
      name: io.opentelemetry.spring-webmvc-5.3
@ -6860,6 +6911,7 @@ libraries:
  - name: spring-webmvc-6.0
    description: |
      This instrumentation enables optional Controller and View (INTERNAL) spans for Spring WebMVC 6.0+.
+    library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/servlet/mvc/package-summary.html
    source_path: instrumentation/spring/spring-webmvc/spring-webmvc-6.0
    minimum_java_version: 17
    scope:
@ -6901,6 +6953,7 @@ libraries:
        - name: spring-webmvc.view.type
          type: STRING
  - name: spring-ws-2.0
+    library_link: https://spring.io/projects/spring-ws
    disabled_by_default: true
    source_path: instrumentation/spring/spring-ws-2.0
    scope:
@ -7424,6 +7477,7 @@ libraries:
  - name: vibur-dbcp-11.0
    description: Instrumentation for the vibur-dbcp library, which provides connection
      pool metrics.
+    library_link: https://www.vibur.org/
    source_path: instrumentation/vibur-dbcp-11.0
    scope:
      name: io.opentelemetry.vibur-dbcp-11.0
--- a/instrumentation/executors/metadata.yaml
+++ b/instrumentation/executors/metadata.yaml
@ -4,7 +4,7 @@ description: >
  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
 configurations:
  - name: otel.instrumentation.executors.include
    description: List of Executor subclasses to be instrumented.
--- a/instrumentation/finagle-http-23.11/metadata.yaml
+++ b/instrumentation/finagle-http-23.11/metadata.yaml
@ -2,3 +2,4 @@ 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
--- a/instrumentation/finatra-2.9/metadata.yaml
+++ b/instrumentation/finatra-2.9/metadata.yaml
@ -1 +1,2 @@
 description: This instrumentation for the Finatra web framework augments the telemetry generated by the underlying Netty instrumentation. It provides more specific, high-level context, such as route information, to the spans generated by Netty.
+library_link: https://github.com/twitter/finatra
--- a/instrumentation/geode-1.4/metadata.yaml
+++ b/instrumentation/geode-1.4/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables database client spans and database client metrics for Apache Geode cache operations.
+library_link: https://geode.apache.org/
 configurations:
  - name: otel.instrumentation.common.db-statement-sanitizer.enabled
    description: Enables statement sanitization for database queries.
--- a/instrumentation/grails-3.0/metadata.yaml
+++ b/instrumentation/grails-3.0/metadata.yaml
@ -1,6 +1,7 @@
 description: >
  This instrumentation enriches existing HTTP server spans with HTTP route information, and
  optionally enables experimental controller (INTERNAL) spans for Grails applications.
+library_link: https://grails.apache.org/
 configurations:
  - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
    description: Enables the creation of experimental controller (INTERNAL) spans.
--- a/instrumentation/graphql-java/graphql-java-20.0/metadata.yaml
+++ b/instrumentation/graphql-java/graphql-java-20.0/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables spans for GraphQL Java operations.
+library_link: https://www.graphql-java.com/
 configurations:
  - name: otel.instrumentation.graphql.query-sanitizer.enabled
    description: Enables sanitization of sensitive information from queries so they aren't added as span attributes.
--- a/instrumentation/grizzly-2.3/metadata.yaml
+++ b/instrumentation/grizzly-2.3/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables HTTP server spans and HTTP server metrics for Grizzly applications.
+library_link: https://javaee.github.io/grizzly/httpserverframework.html
 configurations:
  - name: otel.instrumentation.http.known-methods
    description: >
--- a/instrumentation/grpc-1.6/metadata.yaml
+++ b/instrumentation/grpc-1.6/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables RPC client spans and metrics, and RPC server spans and metrics for gRPC version 1.6 and above.
+library_link: https://github.com/grpc/grpc-java
 configurations:
  - name: otel.instrumentation.grpc.emit-message-events
    type: boolean
--- a/instrumentation/gwt-2.0/metadata.yaml
+++ b/instrumentation/gwt-2.0/metadata.yaml
@ -1 +1,2 @@
 description: This instrumentation enables RPC server spans for GWT RPC requests.
+library_link: https://www.gwtproject.org/
--- a/instrumentation/hibernate/hibernate-3.3/metadata.yaml
+++ b/instrumentation/hibernate/hibernate-3.3/metadata.yaml
@ -1,6 +1,7 @@
 description: >
  This instrumentation enables the generation of INTERNAL spans for Hibernate operations, including
  session methods (e.g., `save`, `update`, `delete`), transaction commits, and query executions.
+library_link: https://github.com/hibernate/hibernate-orm
 configurations:
  - name: otel.instrumentation.hibernate.experimental-span-attributes
    type: boolean
--- a/instrumentation/hibernate/hibernate-4.0/metadata.yaml
+++ b/instrumentation/hibernate/hibernate-4.0/metadata.yaml
@ -1,6 +1,7 @@
 description: >
  This instrumentation enables the generation of INTERNAL spans for Hibernate operations, including
  session methods (e.g., `save`, `update`, `delete`), transaction commits, and query executions.
+library_link: https://github.com/hibernate/hibernate-orm
 configurations:
  - name: otel.instrumentation.hibernate.experimental-span-attributes
    type: boolean
--- a/instrumentation/hibernate/hibernate-6.0/metadata.yaml
+++ b/instrumentation/hibernate/hibernate-6.0/metadata.yaml
@ -1,6 +1,7 @@
 description: >
  This instrumentation enables the generation of INTERNAL spans for Hibernate operations, including
  session methods (e.g., `save`, `update`, `delete`), transaction commits, and query executions.
+library_link: https://github.com/hibernate/hibernate-orm
 configurations:
  - name: otel.instrumentation.hibernate.experimental-span-attributes
    type: boolean
--- a/instrumentation/hibernate/hibernate-procedure-call-4.3/metadata.yaml
+++ b/instrumentation/hibernate/hibernate-procedure-call-4.3/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables the generation of INTERNAL spans for Hibernate stored procedure calls.
+library_link: https://github.com/hibernate/hibernate-orm
 configurations:
  - name: otel.instrumentation.hibernate.experimental-span-attributes
    type: boolean
--- a/instrumentation/hibernate/hibernate-reactive-1.0/metadata.yaml
+++ b/instrumentation/hibernate/hibernate-reactive-1.0/metadata.yaml
@ -1,3 +1,4 @@
 description: >
  This instrumentation does not emit any telemetry on its own. Instead, it enables context
  propagation for Hibernate Reactive asynchronous operations.
+library_link: https://hibernate.org/reactive/
--- a/instrumentation/hikaricp-3.0/metadata.yaml
+++ b/instrumentation/hikaricp-3.0/metadata.yaml
@ -2,3 +2,4 @@ description: >
  This instrumentation provides database client metrics for HikariCP 3.0+ connection pools. It
  reports metrics like connection timeouts, creation time, wait time, and usage time, along with
  connection pool statistics such as the number of active, idle, and pending connections.
+library_link: https://github.com/brettwooldridge/HikariCP
--- a/instrumentation/http-url-connection/metadata.yaml
+++ b/instrumentation/http-url-connection/metadata.yaml
@ -1,6 +1,7 @@
 description: >
  This instrumentation enables the generation of HTTP client spans and HTTP client metrics for
  requests made using `java.net.HttpURLConnection`.
+library_link: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/net/HttpURLConnection.html
 configurations:
  - name: otel.instrumentation.http.known-methods
    description: >
--- a/instrumentation/hystrix-1.4/metadata.yaml
+++ b/instrumentation/hystrix-1.4/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables the generation of INTERNAL spans for Hystrix command executions and fallbacks.
+library_link: https://github.com/Netflix/Hystrix
 configurations:
  - name: otel.instrumentation.hystrix.experimental-span-attributes
    description: Enables capturing the experimental `hystrix.command`, `hystrix.circuit_open` and `hystrix.group` span attributes.
--- a/instrumentation/influxdb-2.4/metadata.yaml
+++ b/instrumentation/influxdb-2.4/metadata.yaml
@ -1 +1,2 @@
 description: This instrumentation enables the generation of database client spans and metrics for the InfluxDB Java client.
+library_link: https://github.com/influxdata/influxdb-java
--- a/instrumentation/java-http-client/metadata.yaml
+++ b/instrumentation/java-http-client/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables HTTP client spans and HTTP client metrics for requests made using the Java HTTP client.
+library_link: https://docs.oracle.com/en/java/javase/11/docs/api/java.net.http/java/net/http/package-summary.html
 configurations:
  - name: otel.instrumentation.http.known-methods
    description: >
--- a/instrumentation/java-http-server/metadata.yaml
+++ b/instrumentation/java-http-server/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables HTTP server spans and HTTP server metrics for the Java HTTP server.
+library_link: https://docs.oracle.com/en/java/javase/21/docs/api/jdk.httpserver/module-summary.html
 configurations:
  - name: otel.instrumentation.http.known-methods
    description: >
--- a/instrumentation/javalin-5.0/metadata.yaml
+++ b/instrumentation/javalin-5.0/metadata.yaml
@ -1 +1,2 @@
 description: This instrumentation enriches existing HTTP server spans with route information, it does not emit any telemetry on its own.
+library_link: https://javalin.io/
--- a/instrumentation/jdbc/metadata.yaml
+++ b/instrumentation/jdbc/metadata.yaml
@ -5,6 +5,7 @@ description: >
  
  There is also a "jdbc-datasource" instrumentation that creates spans for datasource connections,
  but is disabled by default due to the volume of telemetry produced.
+library_link: https://docs.oracle.com/javase/8/docs/api/java/sql/package-summary.html
 configurations:
  - name: otel.instrumentation.jdbc.statement-sanitizer.enabled
    description: Enables statement sanitization for database queries. Takes precedent to 
--- a/instrumentation/kafka/kafka-clients/kafka-clients-0.11/metadata.yaml
+++ b/instrumentation/kafka/kafka-clients/kafka-clients-0.11/metadata.yaml
@ -1,6 +1,7 @@
 description: >
  This instrumentation enables messaging spans and metrics for Apache Kafka 0.11 clients.
  It automatically traces message production and consumption, propagates context, and emits metrics for production and consumption.
+library_link: https://kafka.apache.org/
 configurations:
  - name: otel.instrumentation.kafka.producer-propagation.enabled
    description: Enable context propagation for kafka message producers.
--- a/instrumentation/kafka/kafka-clients/kafka-clients-2.6/metadata.yaml
+++ b/instrumentation/kafka/kafka-clients/kafka-clients-2.6/metadata.yaml
@ -1,5 +1,6 @@
 description: >
  This instrumentation provides a library integration that enables messaging spans and metrics for Apache Kafka 2.6+ clients.
+library_link: https://kafka.apache.org/
 configurations:
  - name: otel.instrumentation.messaging.experimental.capture-headers
    description: A comma-separated list of header names to capture as span attributes.
--- a/instrumentation/kafka/kafka-streams-0.11/metadata.yaml
+++ b/instrumentation/kafka/kafka-streams-0.11/metadata.yaml
@ -0,0 +1 @@
+library_link: https://kafka.apache.org/documentation/streams/
--- a/instrumentation/openai/openai-java-1.1/metadata.yaml
+++ b/instrumentation/openai/openai-java-1.1/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables Gen AI client spans and metrics for OpenAI Java SDK 1.1+.
+library_link: https://github.com/openai/openai-java
 configurations:
  - name: otel.instrumentation.genai.capture-message-content
    type: boolean
--- a/instrumentation/oracle-ucp-11.2/metadata.yaml
+++ b/instrumentation/oracle-ucp-11.2/metadata.yaml
@ -1 +1,2 @@
 description: The Oracle Universal Connection Pool (UCP) instrumentation generates connection pool metrics.
+library_link: https://docs.oracle.com/database/121/JJUCP/
--- a/instrumentation/oshi/metadata.yaml
+++ b/instrumentation/oshi/metadata.yaml
@ -4,3 +4,4 @@ configurations:
    description: Enable the OSHI process runtime metrics.
    type: boolean
    default: false
+library_link: https://github.com/oshi/oshi/
--- a/instrumentation/spark-2.3/metadata.yaml
+++ b/instrumentation/spark-2.3/metadata.yaml
@ -1,3 +1,4 @@
 description: > 
  This instrumentation does not emit telemetry on its own. Instead, it extracts the HTTP route and
  attaches it to HTTP server spans and HTTP server metrics.
+library_link: https://sparkjava.com/
--- a/instrumentation/spring/spring-batch-3.0/metadata.yaml
+++ b/instrumentation/spring/spring-batch-3.0/metadata.yaml
@ -1,5 +1,6 @@
 disabled_by_default: true
 description: This instrumentation enables INTERNAL spans for jobs run by the Spring Batch framework.
+library_link: https://spring.io/projects/spring-batch
 configurations:
  - name: otel.instrumentation.spring-batch.experimental-span-attributes
    type: boolean
--- a/instrumentation/spring/spring-boot-actuator-autoconfigure-2.0/metadata.yaml
+++ b/instrumentation/spring/spring-boot-actuator-autoconfigure-2.0/metadata.yaml
@ -2,3 +2,4 @@ disabled_by_default: true
 description: >
  This instrumentation configures the OpenTelemetry Micrometer bridge to receive metrics from
  Spring Boot Actuator. It does not produce telemetry on its own.
+library_link: https://spring.io/projects/spring-boot
--- a/instrumentation/spring/spring-boot-autoconfigure/metadata.yaml
+++ b/instrumentation/spring/spring-boot-autoconfigure/metadata.yaml
@ -2,3 +2,4 @@ description: >
  This instrumentation auto-configures OpenTelemetry instrumentation for spring-web, spring-webmvc,
  and spring-webflux to instrument Spring Boot applications. It does not produce telemetry on its
  own. This instrumentation is mostly used as part of the Spring Boot starter.
+library_link: https://spring.io/projects/spring-boot
--- a/instrumentation/spring/spring-boot-resources/metadata.yaml
+++ b/instrumentation/spring/spring-boot-resources/metadata.yaml
@ -11,4 +11,4 @@ description: >
    - Check for application.yml in the current working dir
    - Check for --spring.application.name program argument (not jvm arg) via ProcessHandle
    - Check for --spring.application.name program argument via sun.java.command system property
-
+library_link: https://spring.io/projects/spring-boot
--- a/instrumentation/spring/spring-cloud-aws-3.0/metadata.yaml
+++ b/instrumentation/spring/spring-cloud-aws-3.0/metadata.yaml
@ -2,3 +2,4 @@ description: >
  This instrumentation enhances tracing for Spring Cloud AWS. It augments the existing AWS SDK
  instrumentation by providing higher-level tracing for SQS operations, capturing details specific
  to Spring Cloud AWS SQS usage and linking them to the underlying AWS SDK traces.
+library_link: https://spring.io/projects/spring-cloud-aws
--- a/instrumentation/spring/spring-cloud-gateway/spring-cloud-gateway-2.0/metadata.yaml
+++ b/instrumentation/spring/spring-cloud-gateway/spring-cloud-gateway-2.0/metadata.yaml
@ -2,6 +2,7 @@ description: >
  This instrumentation enhances tracing for Spring Cloud Gateway. It does not generate new telemetry
  on its own, but rather enriches existing traces produced by other instrumentations like Netty and
  Spring WebFlux with Spring Cloud Gateway-specific attributes.
+library_link: https://github.com/spring-cloud/spring-cloud-gateway
 configurations:
  - name: otel.instrumentation.spring-cloud-gateway.experimental-span-attributes
    type: boolean
--- a/instrumentation/spring/spring-cloud-gateway/spring-cloud-gateway-2.2/metadata.yaml
+++ b/instrumentation/spring/spring-cloud-gateway/spring-cloud-gateway-2.2/metadata.yaml
@ -2,6 +2,7 @@ description: >
  This instrumentation enhances tracing for Spring Cloud Gateway. It does not generate new telemetry
  on its own, but rather enriches existing traces produced by other instrumentations like Netty and
  Spring WebFlux with Spring Cloud Gateway-specific attributes.
+library_link: https://github.com/spring-cloud/spring-cloud-gateway
 configurations:
  - name: otel.instrumentation.spring-cloud-gateway.experimental-span-attributes
    type: boolean
--- a/instrumentation/spring/spring-core-2.0/metadata.yaml
+++ b/instrumentation/spring/spring-core-2.0/metadata.yaml
@ -3,3 +3,4 @@ description: >
  within Spring Core. It modifies how tasks are submitted and executed to ensure that
  spans created by other instrumentations are correctly linked across thread boundaries,
  rather than generating any new telemetry itself.
+library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/core/package-summary.html
--- a/instrumentation/spring/spring-data/spring-data-1.8/metadata.yaml
+++ b/instrumentation/spring/spring-data/spring-data-1.8/metadata.yaml
@ -2,3 +2,4 @@ description: >
  This instrumentation enhances tracing for Spring Data operations. It works in conjunction
  with other instrumentations, such as JDBC, to provide additional context and details
  for database interactions initiated through Spring Data.
+library_link: https://spring.io/projects/spring-data
--- a/instrumentation/spring/spring-data/spring-data-3.0/metadata.yaml
+++ b/instrumentation/spring/spring-data/spring-data-3.0/metadata.yaml
@ -0,0 +1 @@
+library_link: https://spring.io/projects/spring-data
--- a/instrumentation/spring/spring-integration-4.1/metadata.yaml
+++ b/instrumentation/spring/spring-integration-4.1/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables producer and consumer messaging spans for Spring Integration.
+library_link: https://spring.io/projects/spring-integration
 configurations:
  - name: otel.instrumentation.spring-integration.producer.enabled
    type: boolean
--- a/instrumentation/spring/spring-jms/spring-jms-2.0/metadata.yaml
+++ b/instrumentation/spring/spring-jms/spring-jms-2.0/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables the generation of consumer messaging spans for Spring JMS.
+library_link: https://docs.spring.io/spring-framework/reference/integration/jms.html
 configurations:
  - name: otel.instrumentation.messaging.experimental.receive-telemetry.enabled
    description: >
--- a/instrumentation/spring/spring-jms/spring-jms-6.0/metadata.yaml
+++ b/instrumentation/spring/spring-jms/spring-jms-6.0/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables the generation of consumer messaging spans for Spring JMS.
+library_link: https://docs.spring.io/spring-framework/reference/integration/jms.html
 configurations:
  - name: otel.instrumentation.messaging.experimental.receive-telemetry.enabled
    description: >
--- a/instrumentation/spring/spring-kafka-2.7/metadata.yaml
+++ b/instrumentation/spring/spring-kafka-2.7/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables consumer messaging spans for Spring Kafka listeners.
+library_link: https://spring.io/projects/spring-kafka
 configurations:
  - name: otel.instrumentation.messaging.experimental.receive-telemetry.enabled
    description: >
--- a/instrumentation/spring/spring-pulsar-1.0/metadata.yaml
+++ b/instrumentation/spring/spring-pulsar-1.0/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables consumer messaging spans for Spring Pulsar listeners.
+library_link: https://spring.io/projects/spring-pulsar
 configurations:
  - name: otel.instrumentation.messaging.experimental.receive-telemetry.enabled
    description: >
--- a/instrumentation/spring/spring-rabbit-1.0/metadata.yaml
+++ b/instrumentation/spring/spring-rabbit-1.0/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables consumer messaging spans for Spring RabbitMQ listeners.
+library_link: https://spring.io/projects/spring-amqp
 configurations:
  - name: otel.instrumentation.messaging.experimental.capture-headers
    description: A comma-separated list of header names to capture as span attributes.
--- a/instrumentation/spring/spring-rmi-4.0/metadata.yaml
+++ b/instrumentation/spring/spring-rmi-4.0/metadata.yaml
@ -1 +1,2 @@
 description: This instrumentation enables RPC client and RPC server spans for Spring RMI applications.
+library_link: https://docs.spring.io/spring-framework/docs/4.0.x/javadoc-api/org/springframework/remoting/rmi/package-summary.html
--- a/instrumentation/spring/spring-scheduling-3.1/metadata.yaml
+++ b/instrumentation/spring/spring-scheduling-3.1/metadata.yaml
@ -1,4 +1,5 @@
 description: This instrumentation enables tracing for Spring Scheduling tasks.
+library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/scheduling/package-summary.html
 configurations:
  - name: otel.instrumentation.spring-scheduling.experimental-span-attributes
    description: Adds the experimental span attribute `job.system` with the value `spring_scheduling`.
--- a/instrumentation/spring/spring-security-config-6.0/metadata.yaml
+++ b/instrumentation/spring/spring-security-config-6.0/metadata.yaml
@ -3,6 +3,7 @@ description: >
  attributes, and is only enabled when at least one of the `enduser` configurations is enabled.
  
  NOTE: The `enduser` attributes have been deprecated and will be removed in 3.0+ of the java agent.
+library_link: https://spring.io/projects/spring-security
 configurations:
  - name: otel.instrumentation.common.enduser.id.enabled
    description: Enables capturing the enduser.id attribute.
--- a/instrumentation/spring/spring-web/spring-web-3.1/metadata.yaml
+++ b/instrumentation/spring/spring-web/spring-web-3.1/metadata.yaml
@ -2,3 +2,4 @@ description: >
  This instrumentation provides a library integration that enables capturing HTTP client spans and
  metrics for Spring's RestTemplate. The agent integration enriches HTTP server spans and metrics
  with route information.
+library_link: https://github.com/spring-projects/spring-framework
--- a/instrumentation/spring/spring-web/spring-web-6.0/metadata.yaml
+++ b/instrumentation/spring/spring-web/spring-web-6.0/metadata.yaml
@ -1 +1,2 @@
 description: This instrumentation enriches HTTP server spans and metrics with route information.
+library_link: https://github.com/spring-projects/spring-framework
--- a/instrumentation/spring/spring-webflux/spring-webflux-5.0/metadata.yaml
+++ b/instrumentation/spring/spring-webflux/spring-webflux-5.0/metadata.yaml
@ -1,6 +1,7 @@
 description: > 
  This instrumentation enables HTTP client spans and metrics for Spring WebFlux 5.0. It also
  optionally enables experimental controller (INTERNAL) spans.
+library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/reactive/package-summary.html
 configurations:
  - name: otel.instrumentation.common.experimental.controller-telemetry.enabled
    description: Enables the creation of experimental controller (INTERNAL) spans.
--- a/instrumentation/spring/spring-webflux/spring-webflux-5.3/metadata.yaml
+++ b/instrumentation/spring/spring-webflux/spring-webflux-5.3/metadata.yaml
@ -1,3 +1,4 @@
 description: >
  This instrumentation provides a library integration for the Spring WebFlux WebClient and Webflux
  server versions 5.3+ that enables HTTP client and server spans and metrics.
+library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/reactive/package-summary.html
--- a/instrumentation/spring/spring-webmvc/spring-webmvc-3.1/metadata.yaml
+++ b/instrumentation/spring/spring-webmvc/spring-webmvc-3.1/metadata.yaml
@ -1,5 +1,6 @@
 description: >
  This instrumentation enables optional Controller and View (INTERNAL) spans for Spring WebMVC 3.1+.
+library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/servlet/mvc/package-summary.html
 configurations:
  - name: otel.instrumentation.spring-webmvc.experimental-span-attributes
    type: boolean
--- a/instrumentation/spring/spring-webmvc/spring-webmvc-5.3/metadata.yaml
+++ b/instrumentation/spring/spring-webmvc/spring-webmvc-5.3/metadata.yaml
@ -2,3 +2,4 @@ description: >
  This instrumentation provides a library integration for Spring WebMVC controllers, that enables
  the creation of HTTP server spans and metrics for requests processed by the Spring servlet
  container.
+library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/servlet/mvc/package-summary.html
--- a/instrumentation/spring/spring-webmvc/spring-webmvc-6.0/metadata.yaml
+++ b/instrumentation/spring/spring-webmvc/spring-webmvc-6.0/metadata.yaml
@ -15,3 +15,4 @@ configurations:
    description: Enables the creation of experimental view (INTERNAL) spans.
    type: boolean
    default: false
+library_link: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/servlet/mvc/package-summary.html
--- a/instrumentation/spring/spring-ws-2.0/metadata.yaml
+++ b/instrumentation/spring/spring-ws-2.0/metadata.yaml
@ -1 +1,2 @@
 disabled_by_default: true
+library_link: https://spring.io/projects/spring-ws
--- a/instrumentation/vibur-dbcp-11.0/metadata.yaml
+++ b/instrumentation/vibur-dbcp-11.0/metadata.yaml
@ -1 +1,2 @@
 description: Instrumentation for the vibur-dbcp library, which provides connection pool metrics.
+library_link: https://www.vibur.org/
				`@ -0,0 +1 @@`
				`library_link: https://kafka.apache.org/documentation/streams/`
				`@ -0,0 +1 @@`
				`library_link: https://spring.io/projects/spring-data`