anchor.diff:  called the "Metrics Exporter". Thus you will get an agent that collects inventory and stores it in Hawkular,
   but you will also have a metrics exporter that will be used to expose metrics for collection by Hawkular's Prometheus Server.
   
  -The agent determines what configuration files to pull down via the settings in the local agent configuration file:
  +The agent determines what configuration files to pull down via the settings in the local agent configuration file. The local agent configuration file is the one referred to in the javaagent command line - it is where you told the agent to find the configuration file. e.g. `javaagent:hawkular-javaagent.jar=config=this-config-file.yaml,delay=10`:
   
   ```
   subsystem:
  
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: 
  ```
  
  If you are running WildFly in domain mode, the host controller's domain.conf file should have something like:
  
  ```
  HOST_CONTROLLER_JAVA_OPTS="$HOST_CONTROLLER_JAVA_OPTS -Dhawkular.agent.metadata.domain=true \
  