Currently, a matrix of re-execution tests created from the same workflow link a Grafana URL that includes a set of pre-supplied labels and attempts to show the metrics from that specific job.

However, since multiple jobs in the same matrix share an identical jobID they end up with the same workflow and jobID and the linked Grafana URL shows metrics across multiple re-execution runs, which may produce an inaccurate view of what the user is trying to see. For example, if a workflow triggers jobs multiple distinct ranges of blocks, users should see metrics from those two distinct ranges and not conflate mgas/s across two different ranges. Since the C-Chain dashboard frequently uses aggregates, this results in a particularly inaccurate view.

Each individual job does receive a unique network_uuid and this is already included as a label on the exported metrics, so adding the network_uuid to the set of labels included in the Grafana URL should be sufficient to differentiate them.