anchor.diff:  For this to work, the packets from Ganglia need to have a large enough TTL to be seen on the host where you run pTrans.
   
   Excerpt from gmond.conf:
  -
   ----
   udp_send_channel {
    mcast_join = 239.2.11.71
  
positive.code: 
  You need to configure syslog to forward you the messages.
  For this you need to edit `/ec/syslog.conf` and add a line like this:
  
    *.info          @127.0.0.1:5140
  
  (the facility and severity may vary depending on how your application is logging the metrics)
  
  ==== Manually testing
  
  On a *nix command line you can run
  
    $ logger -p local3.info "type=metric thread.count=7 thread.active=5 heap.permgen.size=20000000"
  
  to add entries to syslog for testing purposes.
  
  
  === Graphite
  
  The converter also accepts Graphite plaintext format
  
      path value timestamp_in_s
  
  or with multiple entries per message
  
      path1 value1 timestamp_in_s1
      path2 value2 timestamp_in_s2
  
  === Ganglia
  
  
negative.code: === StatsD
  
  The converter accepts statsD packets sent via UDP (to the UDP port).
  Format is:
  ----
  key:value|type
  ----
  
  Where only key and value are accepted and the type is ignored (for now).
  
  Example command:
  ----
  $ echo "my_time:100|ms" | nc -u4 localhost 8125
  ----
  
  === collectd
  
  You must configure the collectd network plugin to send UDP packets.
  ----
  LoadPlugin network
  <Plugin network>
          <Server "127.0.0.1" "25826">
          </Server>
  </Plugin>
  ----
  
  == Running ptrans for development
  
  Don't forget to start an Hawkular Metrics web server as well.
  
  === With the start script
  
  You can use the provided `start.sh` script to start the server (this will build the source first).
  
  Make sure to specify a configuration file on the command line:
  ----
   $ ./start.sh -c ptrans.conf
  ----
  
  This method does not allow to configure logging and works on *nix systems only.
  
  === With Maven ===
  
  Once the project is built, simply run the following command:
  ----
  mvn exec:java
  ----
  
  By default, the log4j and ptrans.conf files at the project base directory will be used.
  If you want to use your own files:
  ----
  mvn exec:java -Ddev.log4j.configuration=<path to log4j file> -Ddev.ptrans.conf=<path to ptrans.conf>
  ----
  
  