Skip to content

Commit 427c9a0

Browse files
committed
[DOCS] Reorganize EQL requirements page
1 parent a76df69 commit 427c9a0

File tree

1 file changed

+9
-10
lines changed

1 file changed

+9
-10
lines changed

docs/reference/eql/requirements.asciidoc

+9-10
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,15 @@
88

99
experimental::[]
1010

11-
EQL is schemaless and works out-of-the-box with most common log formats. If you
12-
use a standard log format and already know what fields in your index contain
13-
event type and timestamp information, you can skip this page.
11+
EQL is schema-less and works well with most common log formats.
12+
13+
14+
[TIP]
15+
====
16+
While no schema is required to use EQL in {es}, we recommend the
17+
{ecs-ref}[Elastic Common Schema (ECS)]. The EQL search API is designed to work
18+
with core ECS fields by default.
19+
====
1420

1521
[discrete]
1622
[[eql-required-fields]]
@@ -28,10 +34,3 @@ A field containing the event classification, such as `process`, `file`, or
2834
Timestamp::
2935
A field containing the date and/or time the event occurred. This is typically
3036
mapped as a <<date,`date`>> field.
31-
32-
[TIP]
33-
====
34-
While no schema is required to use EQL in {es}, we recommend the
35-
{ecs-ref}[Elastic Common Schema (ECS)]. {es}'s EQL search is designed to work
36-
with core ECS fields by default.
37-
====

0 commit comments

Comments
 (0)