[Maven-extension] Instrument artifact transfers

[cyrille-leclerc]

Component(s)

maven-extension

Is your feature request related to a problem? Please describe.

Instrument artifact transferts to get finer granularity in build execution.

Describe the solution you'd like

Could be implemented implementing the org.eclipse.aether.transfer.TransferListener API.
WARNING this could generate thousands of spans breaking readability of the produced Maven build traces.

TODO verify how the extension can implement an Aether component.

Describe alternatives you've considered

No response

Additional context

No response

[smurf667]

Hi @cyrille-leclerc

Thanks for opening this issue following our brief email exchange.

I don't have an immediate solution to the challenge of having too many transfer spans cluttering the results. One possible approach could be to aggregate them, though this risks losing some useful details (such as timing and location). To address flexibility, I would foresee a configuration switch to enable or disable tracing of transfers.

I've put together a (naive) prototype that I'll share with you privately first. It leverages org.eclipse.aether.transfer.TransferListener to track transfers.

Here's a preview of what it could look like in the Jaeger UI:

[cyrille-leclerc]

Thanks @smurf667!

Would you mind creating a draft PR with your prototype? I would like to test it.

I don't have an immediate solution to the challenge of having too many transfer spans cluttering the results. One possible approach could be to aggregate them, though this risks losing some useful details (such as timing and location). To address flexibility, I would foresee a configuration switch to enable or disable tracing of transfers.

Some ideas that come to my mind:

• As you said, a configuration param to enable/disable tracing of artifact transfer
• A duration threshold to create artifact transfer spans
• Looking at aggregation