Better correlation between node-stats telemetry and tasks being run #603
Description
Currently, it is cumbersome to correlate node-stats telemetry with the task being run when the samples were taken. For instance, I run benchmarks that include multiple tasks, where each task is a search request that gets run e.g. 500 times. The node-stats telemetry includes user-tags, which do help correlate the samples with the specific rally run (as well as the trial-id I think), but the only way to correlate the samples with the query being run is by looking at when they were taken and comparing that with the different tasks and their execution time. That is not practical.
I could structure my benchmark differently and have one task per challenge rather than multiple tasks per challenge, then user-tags would help me do what I want, but I wonder if it would be possible to add the name of the task being executed (and maybe the iteration) when the sample was taken. I guess this gets complicated when multiple tasks get run in parallel though, so maybe this is not feasible.