anchor.diff:  
   === Running in WildFly
   
  -If you are attaching the agent to a WildFly server, you must set some additional settings.
  +If you are attaching the agent to a WildFly server, you must configure some additional settings.
   
   If you are running WildFly in standalone mode, the standalone.conf you should have something like:
   
  
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: :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
  