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.../instrumentation-core
History
Lauri Tulmin e76d3b19d1
Fix ServletContextPath.prepend for app server spans (#2089) 
* ServletContextPath.prepend doesn't work when server span is created from app server integration

* move ServletContextPath context creation to servlet-common, make servlet2&3 depend on servlet-common so that it would be used in tests that depend on servlet3

* fix failing test

* add servlet-common dependency to modules that depend on servlet3

* add servlet-common dependency to mojarra and myfaces

* run context path instrumentation after servlet instrumentation

* add servlet-common dependency to wicket

* move servlet context path handling

* enable jetty instrumentation for all handlers

* run springmvc tests with tomcat integration, fix peer port and peer ip reporting on tomcat

* jetty integration is now enabled for all handlers

* update expected span name

* Revert "jetty integration is now enabled for all handlers"

This reverts commit 82cbb663f5.

* Revert "update expected span name"

This reverts commit c034496fc5.

* Revert "enable jetty instrumentation for all handlers"

This reverts commit 8a3d077600.

* Trigger Build
 		2021-02-15 23:34:15 -08:00
..
reactor-3.1 testing-common refactoring: replace direct AgentTestRunner usage with… (#2134) 2021-02-01 11:32:25 +01:00
servlet-2.2 Fix ServletContextPath.prepend for app server spans (#2089) 2021-02-15 23:34:15 -08:00
README.md Fix typo in readme (#1240) 2020-09-23 15:28:29 +03:00

README.md

Instrumentation Core

These modules for the core logic for library instrumentation. instrumentation should add core logic here which can be set up manually by a user, and agent-specific code for automatically setting up the instrumentation in that folder.

Note, we are currently working on separating instrumentation projects so that their core parts can be accessed by users not using the agent. Due to the current Gradle setup, we have these two top-level folders, instrumentation and instrumentation-core, but eventually we want to move to flattening them into something like

instrumentation/
  aws-sdk/
    aws-sdk-2.2/
      auto/