Skip to content

Update the Security data ingest check in Discover for ES|QL mode #9181

Open

Description

@florent-leborgne

Discover opens in ES|QL mode by default from 9.6 and in serverless (#8973). The "Verify that your data reaches Elastic Security" section of the Security data ingest page needs a closer look for ES|QL mode, beyond the simple query it has today.

Open points:

  • Decide whether the second bullet, about the data view that Elastic Security uses not including a new index, needs an ES|QL equivalent or stays classic mode only. The bullet is about data views.
  • Make the ES|QL check work for each way readers send data. The example for other methods uses filebeat-*, which fits Beats but not a custom index that Logstash or a third-party collector writes to.

Page: solutions/security/get-started/ingest-data-to-elastic-security.md

Related: #9017, #4898, #8973

Activity

  1. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor

    Elastic Docs AI Menu

    Check one box to run an AI workflow for this issue.

    • Scope the docs work (docs-scope). Status: not started.

    Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

  2. added
    triagedTriage has been run on this issue
    Team:SKIIssues owned by the SKI Docs Team
    and removed
    needs-teamIssues pending triage by the Docs Team
    on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Team:SKIIssues owned by the SKI Docs TeamtriagedTriage has been run on this issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions