Add trace spans for items

[mhansen]

with_items commonly adds latency, we should profile each item. We might need an extra callback from the callback library to achieve this though, or we could just fudge it and say when the next task or item starts, the last item has finished.

[louisquentinjoucla]

Hey 👋

With callback v2_runner_item_on_ok, v2_runner_item_on_failed, we have result in params which contains start date, duration, end date etc..., looks promising, so no need to fudge, here is an example with some echo on a loop:

[mhansen]

Oh, neat! I didn't know the params had start date/duration. I was assuming above that we'd need another callback when an item starts, but we won't need that if we use start date / duration in params.

[louisquentinjoucla]

Yea so here is a bad news:
Some modules does not put start date, duration, end date...

So back to the start it is ! Lets try to find another way 😅 . But we should definitely make a list of useful callback we need to open an issue and PR on ansible repo.

[mhansen]

Ah, bother! Thanks for looking into it. I agree, making those feature-requests on Ansible would be a good idea.

…

On Sun, 19 Jun 2022 at 16:28, Quentin Joucla ***@***.***> wrote: Yea so here is a bad news: Some modules does not put start date, duration, end date... So back to the start it is ! Lets try to find another way 😅 . But we should definitely make a list of useful callback we need to open an issue and PR on ansible repo. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAZYOK3QOLCE4KM2VJVSSLVP24YLANCNFSM5FUOWUCA> . You are receiving this because you authored the thread.Message ID: ***@***.***>