Marcin Grzejszczak
Marcin Grzejszczak
**Is your feature request related to a problem? Please describe.** If one wants to just use the semantic conventions JAR, out of the box one gets `opentelemetry-context` and `opentelemetry-api` JARs...
If there are any beans of type `GlobalObservationHandler` or `GlobalKeyValuesProvider` they should be set on the `ObservationRegistry#observationConfig`
related PR: https://github.com/micrometer-metrics/micrometer/pull/3306
Related PRs - [x] https://github.com/micrometer-metrics/micrometer/pull/3293 - [x] https://github.com/micrometer-metrics/tracing/pull/36
fixes #1628
# Introduction With Micrometer 1.10.0 we're introducing a concept of an `Observation` ([you can read more about it here](https://micrometer.io/docs/tracing)). An `Observation` wraps an action that we would like to measure....
Having the following composite setup for config server (2021.0.0, Boot 2.6.3) ```bash $ curl https://start.spring.io/starter.tgz -d dependencies=cloud-config-server,cloud-starter-vault-config \ -d language=java -d type=maven-project -d baseDir=spring-cloud-config-server | tar -xzvf - ``` Annotated...
https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.5.0
Spring Cloud Contract is written in vast majority in Groovy + the contract definition is a Groovy DSL
Projects to consider: Tracing - https://github.com/openzipkin/brave/tree/master/instrumentation/p6spy Tracing & Metrics - https://github.com/gavlyukovskiy/spring-boot-data-source-decorator