anchor.diff: -= Developer guide: creating a new Beat
  +== Create your own Beat
   
   This guide walks you through the steps for creating a new Elastic Beat.  The
   Beats are a collection of lightweight daemons that collect operational data from
  
positive.code: Let's go through each of these methods and look at a sample implementation.
  
  
  == Configuration
  
  The `Config` method deals with the configuration file and optionally with
  custom CLI flags.
  
negative.code: go get github.com/elastic/topbeat
  ----------------------------------------------------------------------
  
  === Overview
  
  At the high level, a simple Beat like Topbeat has two main components: one that
  collects the actual data and the Publisher. They communicate via a Go channel,
  over which _events_ are sent. The Publisher is implemented in libbeat, so you
  typically only have to worry about the logic specific to your Beat. Besides the
  Publisher, libbeat offers common services like configuration management,
  logging, daemonizing/Windows service handling and in the future it will offer
  