anchor.diff:  
   ```
   
  -If you are running WildFly in domain mode, the domain.conf you should have something like:
  +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 \
  
positive.code: 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
  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
  scrape the agent's metrics exporter endpoint, thus the agent's metrics are collected automatically.
  
  === How It Works with WildFly Domain Mode
  
negative.code: :jbake-tags: blog, agent, prometheus, metrics
  
  Now that Hawkular is moving towards integraton with Prometheus as its metrics collection and storage system, the agent
  has had some changes. This document will discuss those changes and how to run the Hawkular Agent, specifically version 2.0.0.Final.
  
  First, the Hawkular Agent now only runs as a javaagent (no longer does it run inside WildFly as a subsystem extension).
  So to run the agent, simply attach it as a javaagent to whatever JVM you want to monitor (be it a WildFly or EAP app server or
  