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/contributing/documenting-instrumentation.md
+23-4Lines changed: 23 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,6 +83,7 @@ instrumentation.
83
83
Example:
84
84
85
85
```yaml
86
+
display_name: "Example Instrumentation"
86
87
description: "This instrumentation enables..."
87
88
semantic_conventions:
88
89
- HTTP_CLIENT_SPANS
@@ -117,6 +118,15 @@ additional_telemetry:
117
118
type: "STRING"
118
119
```
119
120
121
+
### Display Name (optional)
122
+
123
+
Display name is mostly used for UI purposes, and has two main uses:
124
+
125
+
- Providing a more user-friendly name for the instrumentation than the module name
126
+
(e.g., "Apache CXF JAX-RS 2.x" instead of "jaxrs-2.0-cxf-3.2").
127
+
- Collapsing multiple related modules into a single display name
128
+
(e.g., "Akka Actors" for both "akka-actor-2.3" and "akka-actor-fork-join-2.5").
129
+
120
130
### Description (required)
121
131
122
132
At a minimum, every instrumentation metadata file should include a `description`.
@@ -150,6 +160,13 @@ Some notes when writing descriptions:
150
160
the description unless they are essential to understanding the purpose of the instrumentation.
151
161
* It is not usually necessary to include specific library or framework version numbers in the
152
162
description, unless that context is significant in some way.
163
+
* When describing instrumentations with controller or view spans:
164
+
* Always explicitly state that controller/view spans are disabled by default
165
+
* Use the phrase "(controller spans are disabled by default)" or "(view spans are disabled by default)"
166
+
* When an instrumentation has both enabled-by-default features (like HTTP_ROUTE) and disabled-by-default
167
+
features (like CONTROLLER_SPANS or VIEW_SPANS), describe the enabled features first, then the disabled features
168
+
* Example: "This instrumentation enriches HTTP server spans with route information, and enables
169
+
controller spans for Apache CXF JAX-WS web services (controller spans are disabled by default)."
153
170
154
171
155
172
### Semantic Conventions
@@ -185,11 +202,13 @@ the relevant functionality descriptions.
185
202
List of possible options:
186
203
187
204
* `HTTP_ROUTE`: Instrumentation that enriches HTTP spans with route information
188
-
* `EXPERIMENTAL_ONLY`: Instrumentation that is experimental and may not be stable
189
-
* `CONTEXT_PROPAGATION`: Instrumentation that provides context propagation capabilities
205
+
* `CONTEXT_PROPAGATION`: Instrumentation that propagates OpenTelemetry context across application or thread boundaries. This applies to:
206
+
* Inter-process/application context propagation: Passing context through headers between applications (HTTP, gRPC, messaging, etc.)
207
+
* Inter-thread context propagation: Passing context from one thread to another (executors, actors, reactive streams, etc.)
208
+
* Does not include standard single-threaded scope management or normal span creation patterns
190
209
* `AUTO_INSTRUMENTATION_SHIM`: Instrumentation that adapts or bridges instrumentation from upstream libraries or frameworks
191
-
* `CONTROLLER_SPANS`: Instrumentation that generates controller-level spans
192
-
* `VIEW_SPANS`: Instrumentation that generates view-level spans
210
+
* `CONTROLLER_SPANS`: Instrumentation that generates controller-level spans for controller/handler methods in web frameworks (disabled by default, experimental)
211
+
* `VIEW_SPANS`: Instrumentation that generates view-level spans for view rendering such as templates or JSP (disabled by default, experimental)
This instrumentation enables controller spans for Apache Axis2 JAX-WS web services, and enriches HTTP server spans with route information.
4631
+
This instrumentation enriches HTTP server spans with route information, and enables controller spans for Apache Axis2 JAX-WS web services (controller spans are disabled by default).
This instrumentation enables controller spans for Apache CXF JAX-WS web services, and enriches HTTP server spans with route information.
4650
+
This instrumentation enriches HTTP server spans with route information, and enables controller spans for Apache CXF JAX-WS web services (controller spans are disabled by default).
4669
4651
library_link: https://cxf.apache.org/
4670
4652
features:
4671
-
- CONTROLLER_SPANS
4672
-
- CONTEXT_PROPAGATION
4673
4653
- HTTP_ROUTE
4674
-
- EXPERIMENTAL_ONLY
4654
+
- CONTROLLER_SPANS
4675
4655
source_path: instrumentation/jaxws/jaxws-cxf-3.0
4676
4656
scope:
4677
4657
name: io.opentelemetry.jaxws-cxf-3.0
@@ -4683,20 +4663,14 @@ libraries:
4683
4663
description: Enables the creation of experimental controller (INTERNAL) spans.
This instrumentation enables controller spans for methods annotated with the @WebService annotation from the JWS API.
4669
+
This instrumentation enables controller spans for methods annotated with the @WebService annotation from the JWS API (controller spans are disabled by default).
Copy file name to clipboardExpand all lines: instrumentation-docs/src/main/java/io/opentelemetry/instrumentation/docs/internal/InstrumentationFeature.java
0 commit comments