anchor.diff:      </avail-set-dmr>
       <resource-type-set-dmr name="Main" enabled="true">
           <resource-type-dmr name="WildFly Server" resourceNameTemplate="WildFly Server [%ManagedServerName] [${
  -jboss.node.name:localhost}]" path="/" metricSets="WildFly Memory Metrics,WildFly Threading Metrics,WildFly Aggregated 
  +jboss.node.name:localhost}]" path="/" metricSets="WildFly Memory Metrics,WildFly Threading Metrics,WildFly Aggregated
   Web Metrics" availSets="Server Availability">
               <resource-config-dmr name="Hostname" path="/core-service=server-environment" attribute="qualified-
   host-name"/>
  
positive.code: single-node cluster. You do not have to worry about setting up and configuring
  Cassandra before getting started with Hawkular.
  
  For a more proper installation, please refer to link:user/installation.html[the installation guide]
  
  NOTE: The embedded Cassandra is not intended for production use, we definitely recommend to use a separate Cassandra server.
  
  
negative.code: === Error on starting Hawkular- OutOfMemoryError: unable to create new native thread
  This may happen if you use Cassandra embedded with Hawkular on *x systems
  
  Cassandra requres `ulimit` settings that are higher than usual on common *nix distributions. First check your present limits with `ulimit -a` and eventually increase open files to 65535 and max user processes to 4096 as appropriate on your system.
  
  On RHEL, CentOS and Fedora the settings can be made persistent in `/etc/security/limits.conf` like this:
  ----
  