anchor.diff:  [[grok-processor-rest-get]]
   ==== Retrieving patterns from REST endpoint
   
  -The Grok Processor comes packaged with its own REST endpoint for retrieving which patterns the processor is packaged with.
  +The Grok processor comes packaged with its own REST endpoint for retrieving the patterns included with the processor.
   
   [source,console]
   --------------------------------------------------
  
positive.code: https://github.com/elastic/elasticsearch/blob/{branch}/libs/grok/src/main/resources/patterns[reusable patterns].
  
  If you need help building patterns to match your logs, you will find the
  {kibana-ref}/xpack-grokdebugger.html[Grok Debugger] tool quite useful! 
  The https://grokconstructor.appspot.com[Grok Constructor] is also a useful tool.
  
  [[using-grok]]
  
negative.code: }
  --------------------------------------------------
  // NOTCONSOLE
  
  By default, the API returns a list of legacy Grok patterns. These legacy
  patterns predate the {ecs-ref}/ecs-field-reference.html[Elastic Common Schema
  (ECS)] and don't use ECS field names. To return patterns that extract ECS field
  names, specify `v1` in the optional `ecs_compatibility` query parameter.
  
  [source,console]
  ----
  GET _ingest/processor/grok?ecs_compatibility=v1
  ----
  
  By default, the API returns patterns in the order they are read from disk. This
  sort order preserves groupings of related patterns. For example, all patterns
  