anchor.diff:  Let's go through each of these methods and look at a sample implementation.
   
   
  -== Configuration
  +=== Configuration
   
   The `Config` method deals with the configuration file and optionally with
   custom CLI flags.
  
positive.code: <2> The `timestamp` fields needs to be of time `common.Time`.
  <3> Sending the event.
  
  === Cleanup
  
  The `Cleanup` method is executed after the main loop finishes or is interrupted
  and gives you the opportunity to release any resources you might use. For
  
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
  