Lettuce intrumentatio is implemented in a way that after operation has been performed `span` is not closed syncronously - in fact this happens on separate thread. This means `spans` for even syncronous operations may be closed on opposite order. This means that writing tests that pefrom two operations and expect two traces is slightly more complicated. In many places we can just avoid doing that by preparing necessary data in `setup`. This fixes some of the false negatives in tests. |
||
---|---|---|
.circleci | ||
buildSrc | ||
dd-java-agent | ||
dd-java-agent-ittests | ||
dd-trace-api | ||
dd-trace-ot | ||
gradle | ||
.editorconfig | ||
.gitignore | ||
LICENSE | ||
LICENSE-3rdparty.csv | ||
NOTICE | ||
README.md | ||
dd-trace-java.gradle | ||
gradlew | ||
gradlew.bat | ||
settings.gradle |
README.md
Datadog Java APM
To use and configure Datadog Java APM, see https://docs.datadoghq.com/tracing/languages/java