* set root cause as the exception_name in micrometer tags
* set root cause as the exception_name in other metrics system
* set root cause as the exception_name in other metrics system
* Update ExceptionUtilsTest.java
* reformat
* reformat
* add root_cause_name instead of changing exception_name
Co-authored-by: Marvin Froeder <velo@users.noreply.github.com>
* Support of capabilities for AsyncFeign
* Removed SyncBased interface, added todo for stageExecution, and adopted micrometer client to be async as well.
* Added internal builder flag similar to 'forceDecoding' but for client enrichment
* Added async client enrichment to Dropwizard5 capability
* Added async client enrichment to Dropwizard5 capability + code formatting
* Progress with tests; added decoder condition similar to the client one
* Fixed javadoc
* A different take on skipping enrichment and delagation
* Switcharoo
* Relaxed casting requirements and check it during execution phase
* Create class to hold common Builder fields
* Make sure capabilities are applied to all relevant fields
Co-authored-by: Marvin Froeder <velo@users.noreply.github.com>
Co-authored-by: Marvin Froeder <velo.br@gmail.com>
* The counter indicator increases by 2 each time (on happy path).
* Add test coverage
* Make test beaty again
* Fix license header
* Move new tests to the common abstract class
* Use path expression rather than explicit value for Micrometer "uri" labels
* e.g. "/get/{id}" rather than "/get/123"
* this provides better aggregation, protecting the time series database
* Make assertions more self explanatory
* Test Micrometer Decoder uri label
* Move tests to AbstractMetricsTestBase, add uri label to dropwizard-metrics4&5
Co-authored-by: Marvin Froeder <velo@users.noreply.github.com>
* Move hamcrest dependency to the parent, upgrade it to 2.2
* hamcrest-library is deprecated
* organise properties in parent: move the hamcrest version next to other test tools
On previous implementation response code would only be collected for errors.
To avoid mixing new and old metrics, gave the one that includes successfull codes a different name
This change converts the Java11 module release into two steps:
1. run `mvn install` for just feign-java11 to ensure the dependent
projects exist in the local repo
2. run `mvn deploy` for `feign-java11`
The result should be that only the single module is deployed
* Correcting License Headers