Update OTel Spring starter doc with 2.6.0 features (#4847)
Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Co-authored-by: Fabrizio Ferri-Benedetti <fferribenedetti@splunk.com> Co-authored-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
This commit is contained in:
parent
04a6cb63cc
commit
18e6ecd24b
|
@ -18,6 +18,15 @@ Out of the box instrumentation is available for several frameworks:
|
|||
| Micrometer | `otel.instrumentation.micrometer.enabled` | false |
|
||||
| R2DBC (reactive JDBC) | `otel.instrumentation.r2dbc.enabled` | true |
|
||||
|
||||
## Turn on instrumentations selectively
|
||||
|
||||
To use only specific instrumentations, turn off all the instrumentations first
|
||||
by setting the `otel.instrumentation.common.default-enabled` property to
|
||||
`false`. Then, turn on instrumentations one by one.
|
||||
|
||||
For example, if you want to only enable the JDBC instrumentation, set
|
||||
`otel.instrumentation.jdbc.enabled` to `true`.
|
||||
|
||||
## Common instrumentation configuration
|
||||
|
||||
Common properties for all database instrumentations:
|
||||
|
@ -118,6 +127,13 @@ public MyService(RestClient.Builder restClientBuilder) {
|
|||
}
|
||||
```
|
||||
|
||||
As it's possible with the Java agent, you can configure the capture of the
|
||||
following entities:
|
||||
|
||||
- [HTTP request and response headers](/docs/zero-code/java/agent/instrumentation/http/#capturing-http-request-and-response-headers)
|
||||
- [Known HTTP methods](/docs/zero-code/java/agent/instrumentation/http/#configuring-known-http-methods)
|
||||
- [Experimental HTTP telemetry](/docs/zero-code/java/agent/instrumentation/http/#enabling-experimental-http-telemetry)
|
||||
|
||||
## Spring Web MVC Autoconfiguration
|
||||
|
||||
This feature autoconfigures instrumentation for Spring WebMVC controllers by
|
||||
|
@ -129,6 +145,13 @@ request. To learn more about the OpenTelemetry Spring WebMVC instrumentation,
|
|||
see the
|
||||
[opentelemetry-spring-webmvc-5.3 instrumentation library](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/spring/spring-webmvc/spring-webmvc-5.3/library).
|
||||
|
||||
As it's possible with the Java agent, you can configure the capture of the
|
||||
following entities:
|
||||
|
||||
- [HTTP request and response headers](/docs/zero-code/java/agent/instrumentation/http/#capturing-http-request-and-response-headers)
|
||||
- [Known HTTP methods](/docs/zero-code/java/agent/instrumentation/http/#configuring-known-http-methods)
|
||||
- [Experimental HTTP telemetry](/docs/zero-code/java/agent/instrumentation/http/#enabling-experimental-http-telemetry)
|
||||
|
||||
## Spring WebFlux Autoconfiguration
|
||||
|
||||
Provides autoconfigurations for the OpenTelemetry WebClient ExchangeFilter
|
||||
|
|
|
@ -6579,6 +6579,18 @@
|
|||
"StatusCode": 206,
|
||||
"LastSeen": "2024-05-15T19:23:47.920456821+03:00"
|
||||
},
|
||||
"https://opentelemetry.io/docs/zero-code/java/agent/instrumentation/http/#capturing-http-request-and-response-headers": {
|
||||
"StatusCode": 206,
|
||||
"LastSeen": "2024-07-18T12:15:23.404682814Z"
|
||||
},
|
||||
"https://opentelemetry.io/docs/zero-code/java/agent/instrumentation/http/#configuring-known-http-methods": {
|
||||
"StatusCode": 206,
|
||||
"LastSeen": "2024-07-18T12:15:25.914328974Z"
|
||||
},
|
||||
"https://opentelemetry.io/docs/zero-code/java/agent/instrumentation/http/#enabling-experimental-http-telemetry": {
|
||||
"StatusCode": 206,
|
||||
"LastSeen": "2024-07-18T12:15:30.126385341Z"
|
||||
},
|
||||
"https://opentelemetry.io/ecosystem/integrations/": {
|
||||
"StatusCode": 206,
|
||||
"LastSeen": "2024-03-19T10:16:49.992495889Z"
|
||||
|
|
Loading…
Reference in New Issue