anchor.diff:  and the timeout is measured from the time this endpoint starts to process the
   data.
   --
  +
  +
  +[[ml-find-file-structure-example-eslog]]
  +===== Analyzing {es} log files
   
   This is an example of analyzing {es}'s own log file:
   
  
positive.code:   a Grok pattern.
  
  `has_header_row`::
    (boolean) Optional. If you have set `format` to `delimited`, you can use this
    parameter to indicate whether the column names are in the first row of the
    file. If this parameter is not specified, the structure finder guesses based
    on the similarity of the first row of the file to other rows.
  
  `line_merge_size_limit`::
    (unsigned integer) Optional. The maximum number of characters in a message
    when lines are merged to form messages while analyzing semi-structured files.
    The default is `10000`. If you have extremely long messages you may need to
    increase this, but be aware that this may lead to very long processing times
    if the way to group lines into messages is misdetected.
  
  `lines_to_sample`::
    (unsigned integer) Optional. The number of lines to include in the structural
    analysis, starting from the beginning of the file. The minimum is 2; the
    default is `1000`. If the value of this parameter is greater than the number
    of lines in the file, the analysis proceeds (as long as there are at least two
  
negative.code: Finds the structure of a text file. The text file must contain data that is
  suitable to be ingested into {es}.
  
  
  [[ml-find-file-structure-request]]
  ==== {api-request-title}
  
  `POST _ml/find_file_structure`
  
  
  [[ml-find-file-structure-prereqs]]
  ==== {api-prereq-title}
  