Nikita Salnikov-Tarnovski
Nikita Salnikov-Tarnovski
Do current spec versioning and compatibility guidelines say anything about deprecating and removing features with time? Should read it again...
@tigrannajaryan I am thinking about https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/versioning-and-stability.md. Which does not say almost anything about semantic convention :(
> We iterated on this problem in Go SDK and the solution we came up with is to have one semconv package per version > of semantic conventions, see [the...
@open-telemetry/java-instrumentation-maintainers I propose to move this issue to contrib repo. Even if such exporter will be written, it will over there and not in this repo.
One more option to always include manual spans is to use InstrumentationLibrary.Name: if it does not start with `io.opentelemetry`, then return `RECORD`
> > One more option to always include manual spans is to use InstrumentationLibrary.Name: if it does not start with `io.opentelemetry`, then return `RECORD` > > how would you implement...
I have solved this issue by adding `volumes
> current behavior is there since the inception of `report-aggregate` and IMO [clearly stated in documentation](https://www.jacoco.org/jacoco/trunk/doc/report-aggregate-mojo.html) > > > The report is created from all modules this project **depends on**....
Yes, Docker works fine on my machine. And e.g. Testcontainers work as well.
Why these attributes cannot be set in `onStart`, which already has writable span?