You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/instrumentation-list.yaml
+13-13Lines changed: 13 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
libraries:
6
6
activej:
7
7
- name: activej-http-6.0
8
-
description: this instrumentation enables SERVER spans and metrics for the ActiveJ
8
+
description: This instrumentation enables SERVER spans and metrics for the ActiveJ
9
9
HTTP server.
10
10
source_path: instrumentation/activej-http-6.0
11
11
minimum_java_version: 17
@@ -260,7 +260,7 @@ libraries:
260
260
apache:
261
261
- name: apache-dbcp-2.0
262
262
description: |
263
-
this instrumentation enables database connection pools metrics for Apache DBCP.
263
+
This instrumentation enables database connection pools metrics for Apache DBCP.
264
264
The instrumentation uses `MBeanRegistration` methods for lifecycle detection, therefore it only activates if the `BasicDataSource` is registered to an `MBeanServer`. If using Spring Boot, this happens automatically as all Spring beans that support JMX registration are automatically registered by default.
265
265
source_path: instrumentation/apache-dbcp-2.0
266
266
scope:
@@ -382,7 +382,7 @@ libraries:
382
382
- name: rpc.system
383
383
type: STRING
384
384
- name: apache-httpasyncclient-4.1
385
-
description: this instrumentation enables CLIENT spans and metrics for the Apache
385
+
description: This instrumentation enables CLIENT spans and metrics for the Apache
this instrumentation enables tracing for Apache Camel 2.x applications by generating spans for each route execution. For Camel versions 3.5 and newer, users should instead use the native 'camel-opentelemetry' component provided directly by the Camel project.
1122
+
This instrumentation enables tracing for Apache Camel 2.x applications by generating spans for each route execution. For Camel versions 3.5 and newer, users should instead use the native 'camel-opentelemetry' component provided directly by the Camel project.
1123
1123
source_path: instrumentation/camel-2.20
1124
1124
scope:
1125
1125
name: io.opentelemetry.camel-2.20
@@ -1333,7 +1333,7 @@ libraries:
1333
1333
default: false
1334
1334
elasticsearch:
1335
1335
- name: elasticsearch-api-client-7.16
1336
-
description: this instrumentation enables client spans for Elasticsearch API client
1336
+
description: This instrumentation enables client spans for Elasticsearch API client
1337
1337
requests for version 7 of the client. Versions 8.10 and later have native support
this instrumentation enables client spans for Elasticsearch transport client requests. Each call produces a span named after the Elasticsearch action, enriched with transport-specific attributes.
1439
+
This instrumentation enables client spans for Elasticsearch transport client requests. Each call produces a span named after the Elasticsearch action, enriched with transport-specific attributes.
this instrumentation enables client spans for Elasticsearch transport client requests. Each call produces a span named after the Elasticsearch action, enriched with transport-specific attributes.
1515
+
This instrumentation enables client spans for Elasticsearch transport client requests. Each call produces a span named after the Elasticsearch action, enriched with transport-specific attributes.
this instrumentation enables client spans for Elasticsearch transport client requests. Each call produces a span named after the Elasticsearch action, enriched with transport-specific attributes.
1601
+
This instrumentation enables client spans for Elasticsearch transport client requests. Each call produces a span named after the Elasticsearch action, enriched with transport-specific attributes.
0 commit comments