[maven-extension] Disable Mojo spans about opentelemetry-java-contrib

[cyrille-leclerc]

Implemented in

• #108

[cyrille-leclerc]

@v1v @kuisathaverat it reminds me the problem we faced on Jenkins observability. 17k span is one order of magnitude higher than the problem we faced in CI pipeline traces :-)
I like the idea to be incremental and first enable disabling bluntly the mojo spans. Later, we will be able to refine the feature to support smarter filtering if it makes sense.
Note that this telles me that the challenge will come when we add unit test visibility. One span per unit test?

[kenfinnigan]

Ok, I will start playing around with this when I have a moment.

Whether we need a span per unit test would depend on the purpose of the spans.

If it's purely as a view on how long a build is taking, does it need that really fine-grained level of a particular test? Or only all the tests and then recognize if a set of tests takes too long, to evaluate the logs for how long each test actually took to find the culprit?

[cyrille-leclerc]

Thanks @kenfinnigan .

For unit tests, I have in mind reporting on the test executions to help detect flaky tests, slow tests, top failing tests...
I imagine that DevOps tool listening to the stream of CI traces to extract these pieces of information.

I think this project is pursuing a similar goal: https://github.com/rakyll/go-test-trace .