anchor.diff:  }
   ----------------------------------------------------------------------
   
  -We recommend to implement a New function that creates your beats object.
  +We recommend that you implement a `New` function that creates your Beats object.
   
   === Sharing Your Beat with the Community
   
  
positive.code: The `Beat` parameter received by most of these methods contains data about the
  Beat, such as the name, version, and common configuration options.
  
  For more complex beats, the optional FlagsHandler interface is available.
  
  [source,go]
  ----------------------------------------------------------------------
  
negative.code: }
  ----------------------------------------------------------------------
  
  You can use the `FlagsHandler` interface to add additional command line flags to
  your Beat. The `HandleFlags` callback is called after the Beat parses the
  command line arguments inherited from libbeat and handles the `--help` and
  `--version` flags. For an example of how to implement `HandleFlags`, take a look
  at the
  https://github.com/elastic/packetbeat/blob/master/beat/packetbeat.go[Packetbeat]
  code.
  
  We strongly recommend that you create a main package that contains only the main
  method. All your Beat-specific code should go in a separate folder and package.
  This will allow other Beats to use the other parts of your Beat as a library, if
  needed.
  
  NOTE: To be consistent with other Beats, you should append `beat` to your Beat name.
  
  