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
opentelemetry-java-instrume.../smoke-tests
History
Han Zhang 5b1218cdb8
Update instrumentation to be compliant with HTTP semantic conventions (#227) 
* Update HTTP client-side span names

* Add query and fragment to  http.url for HTTP client spans

* Add query and fragment to http.url for HTTP server spans

* Update HTTP server span names to be the matched route or resource

* Use net.peer.* instead of peer.* attributes
 		2020-03-12 18:49:52 -07:00
..
cli Add license headers (#188) 2020-02-27 13:24:42 -08:00
java9-modules Add license headers (#188) 2020-02-27 13:24:42 -08:00
play Update instrumentation to be compliant with HTTP semantic conventions (#227) 2020-03-12 18:49:52 -07:00
springboot Update instrumentation to be compliant with HTTP semantic conventions (#227) 2020-03-12 18:49:52 -07:00
src/main/groovy/io/opentelemetry/smoketest Add license headers (#188) 2020-02-27 13:24:42 -08:00
wildfly Add license headers (#188) 2020-02-27 13:24:42 -08:00
README.md Rename package to io.opentelemetry.auto (#54) 2020-01-14 13:57:01 -08:00
smoke-tests.gradle Removed statically loaded exporters and added more tests (#171) 2020-02-21 15:12:48 -08:00

README.md

Smoke Tests

Assert that various applications will start up with the JavaAgent without any obvious ill effects.

Each subproject underneath smoke-tests is a single smoke test. Each test does the following

  • Launch the application with stdout and stderr logged to $buildDir/reports/server.log
  • For web servers, run a spock test which does 200 requests to an endpoint on the server and asserts on an expected response.

Note that there is nothing special about doing 200 requests. 200 is simply an arbitrarily large number to exercise the server.