Benchmark files containing ip addresses are not very reusable

[davidkel]

Benchmark files should be re-usable assets however configuration for things like prometheus push gateway make that a problem because they define an address of the gateway to push to or a prometheus server where you want to extract information from. It should be possible to override these entries when launching a manager so that a benchmark file can be re-used and can still extract the required information if the network topology changes

A similar problem can also be seen for remote docker monitoring, so a solution is required here that is flexible and addresses the need to define the information to be captured in a single benchmark file

[davidkel]

As a thought we could have benchmark files allow for variable substitution, that variable value could come from

• env vars (both manager and worker)
• parameter provided to manager/worker on launching

In other words, caliper could support benchmark templates along with concrete benchmark files