open-telemetry
/
opentelemetry-java-instrumentation
mirror of https://github.com/open-telemetry/opentelemetry-java-instrumentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add documentation for suppression by type flag (#3990) 

* Update suppressing-instrumentation.md

* lint

* better suppression strategy description
This commit is contained in:
Liudmila Molkova 2021-09-08 12:05:12 -10:00 committed by GitHub
parent 3ae6b46930
commit dc69d5fb56
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/suppressing-instrumentation.md
View File

@ -119,3 +119,8 @@ so that we can try to come up with a better solution to address your need.
You can suppress all auto instrumentations but have support for manual instrumentation with `@WithSpan` and normal API interactions by using
`-Dotel.instrumentation.common.default-enabled=false -Dotel.instrumentation.opentelemetry-annotations.enabled=true`
## Enable instrumentation suppression by type
By default the agent suppresses all nested `CLIENT` instrumentations, without discerning their actual type (e.g. a database `CLIENT` using an HTTP client that generates `CLIENT` spans too).
By setting `-Dotel.instrumentation.experimental.outgoing-span-suppression-by-type=true` you can enable a more sophisticated suppression strategy: only `CLIENT` spans of the same types (e.g. DB, HTTP, RPC) will be suppressed.