Daniel Mitterdorfer

Ah, thanks for the clarification. In any case, I think this should still be implemented in `ClusterEnvironmentInfo`.

I'd be fine either way as long as the file name is not hardcoded in Rally. I'd treat my summary above as a proposal / hint rather than a prescription...

> A new configuration file would be in the release notes, hopefully? Even if that would be the case, we benchmark against master so by the time we see the...

> I don't know what makes Docker different here, sorry. The config files are already embedded in the Docker image. I think it's sufficient that we just don't provide a...

> It's also worth considering renaming the parameter to target. This would be a breaking change, however, so there's a cost-benefit analysis to be done. Curious what others think. I'm...

Thanks for the issue! Given that Rally handles this gracefully already there is no immediate urgency to remove it. This also means that https://github.com/elastic/elasticsearch/pull/75274 can be merged at any time....

In the *very* early days of Rally, it brought a sample dashboard but it turned out that it is not really helpful. Rally is agnostic to the benchmarks it runs...

We discussed this in our sync and came up with a modification of proposal number one defined above. Instead of introducing a separate structure for `task` we'll introduce a separate...