Skip to content

Bug in "fields" - EQL #72864

@srikwit

Description

@srikwit

Dear Team,

From the documentation at https://www.elastic.co/guide/en/elasticsearch/reference/master/eql.html#retrieve-selected-fields

I am trying to use the fields option in EQL but I am getting an error as follows, I have followed the documentation and I am providing the differences against regular search for your reference:

  1. Regular fields - works
GET winlogbeat-7.12.0/_search
{
  "fields": []
}
  1. EQL fields - Does not work
GET winlogbeat-7.12.0/_eql/search
{
  "fields": []
}

{
  "error" : {
    "root_cause" : [
      {
        "type" : "x_content_parse_exception",
        "reason" : "[2:3] [eql/search] unknown field [fields]"
      }
    ],
    "type" : "x_content_parse_exception",
    "reason" : "[2:3] [eql/search] unknown field [fields]"
  },
  "status" : 400
}

I have simplified the example from the documentation and the issue I find is with the following description:
You can also use the fields parameter to retrieve and format specific fields in the response. This field is identical to the search API’s fields parameter.

I would also like to point out that the fields option is never populated from the console when we type the name in the standard search as well as EQL search which I have uploaded for your reference.

image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions