* Akka http server span names are always akka.request #3478
- removed hardcoded span name "akka.request"
- implemented route() in AkkaHttpServerAttributesExtractor to provide a better span name
- retrofitted AkkaHttpServerInstrumentationTest.groovy
* Akka http server span names are always akka.request #3478
- removed hardcoded span name "akka.request" and changed to "HTTP {METHOD}"
- retrofitted AkkaHttpServerInstrumentationTest.groovy
* Akka http server span names are always akka.request #3478
- removed hardcoded span name "akka.request" and changed to "HTTP {METHOD}"
- retrofitted AkkaHttpServerInstrumentationTest.groovy
* Akka http server span names are always akka.request #3478
- removed hardcoded span name "akka.request" and changed to "HTTP {METHOD}"
- retrofitted AkkaHttpServerInstrumentationTest.groovy and related tests
* Add Ratpack HttpClient instrumentation
* Propagate trace through Ratpack HttpClient
* Add test to verify trace propagation
* Fix spotlessApply
* Use HTTP method as name for ratpack http client
* Add current Context to the execution
* Fix HttpClient tests
* Move Ratpack HttpClient tests to java package
* Remove nullaway conventions from library
* Add Context to ExecHarness executions
* Remove ContextHolder from execution
* Fix function test using other server stub
* Fix lazy other app
* Refactor ratpack client packages
* Rename getter method
* Spring RMI instrumentation
* Change the order of import statements
* remove extra separation in import statements
* stylistic changes
* Fix groovy rule violations
* Formatting changes in groovy file
* Spotless fixes and muzzle check version change
* Fixed minimum version in filenames and fixed muzzle check
* single InstrumentationModule and added context propagation test
* Merged singletons, use random port in test and add stricter matchers.
* Remove unused import
Adds `FAIL_ON_UNKNOWN_PROPERTIES` to the paramter parser on the lambda
as events coming from AWS have more fields than those represented in the
libraries provided by AWS. Adds a custom `JodaModule` to the same
parser to support `ScheduledEvent` which for now uses Joda Time. At the
same time avoid the real Joda Module to not have extra dependencies.
Resolves: https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/4645
* Add `http.route` to the server span when `ServerSpanNaming` is updated
* fix camel tests
* fix test compilation failure
* assert route in camel instrumentation
* during install, hook up the log emitter provider for instrumentation to use.
* spotless
* Fix tests
* Default instrumentation name to ROOT when logger name null/empty
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
* rename artifacts and packages
* Library users shouldn't need to use internal
* Update docs
* Rename in order to simplify HelperClassPredicate
* Spotless
* Move AgentLogEmitterProvider to javaagent-instrumentation-api
* Micrometer instrumentation, part 2
* use double counter instead of gauge in FunctionTimer
* code review suggestions
* fix errorprone
* rebase and fix compilation failure
Mateusz Rzeszutek
Matthew Ho
jack-berg
Lauri Tulmin
jason plumb
Trask Stalnaker
Anuraag Agrawal
Christian Frommeyer
Amir Blum
Javier Salinas
Samudraneel Dasgupta
acm19
Nikita Salnikov-Tarnovski