anchor.diff:  added, additional configuration files are loaded on the Hawkular Server which can then be pulled down by the agent
   by simply changing the values of these `type-version` and `config-file` settings.
   
  -NOTE: Note that a WildFly host controller must be told to download the metrics exporter
  +NOTE: Note that a WildFly host controller agent must be told to download the metrics exporter
   config file of "WF10-DOMAIN" while the type-version should still be "WF10".
   See the WildFly+Agent distro (Maven artifact org.hawkular.agent:hawkular-javaagent-wildfly-dist) as an example.
   
  -When the agent itself is registered in inventory on the Hawkular Server, Hawkular's Prometheus Server will be told to
  +When an agent itself is registered in inventory on the Hawkular Server, Hawkular's Prometheus Server will be told to
   scrape the agent's metrics exporter endpoint, thus the agent's metrics are collected automatically.
   
   === How It Works with WildFly Domain Mode
  
positive.code:     data-dir: ${jboss.domain.base.dir}/data/hawkular-metrics-exporter
  ```
  
  The host controller's agent must turn on the Prometheus JMX Exporter in "master proxy mode"
  
  ```
  metrics-exporter:
  
negative.code:     data-dir: ${jboss.domain.data.dir}/hawkular-metrics-exporter
  ```
  
  Note the data directories between the slaves and master must be the same. It is recommended to use a subdirectory under WildFly's domain/data directory as you see in the examples above.
  
  What happens under the covers is the slave server will write a file to the data directory describing the
  metrics exporter endpoint it started. The master will collect this information from all slaves and makes
  