From 708e08b871249817b77fff6e3524e92d48dd441f Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Tue, 31 Oct 2023 14:55:15 +0000 Subject: [PATCH] Adds link to Endpoint event documentation (#4105) (#4139) * Adds link to Endpoint event documentation * Updates terminology (cherry picked from commit 9f39ec13472a3c6e7b3bbb43bc6adf7f76fe3d49) Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com> --- docs/reference/field-ref.asciidoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/reference/field-ref.asciidoc b/docs/reference/field-ref.asciidoc index 0a215f6c9f..eb95040920 100644 --- a/docs/reference/field-ref.asciidoc +++ b/docs/reference/field-ref.asciidoc @@ -7,6 +7,8 @@ This section lists {ecs-ref}[Elastic Common Schema] (ECS) fields used by {elasti IMPORTANT: We recommend you use {agent} integrations or {beats} to ship your data to {elastic-sec}. {agent} integrations and Beat modules (for example, {filebeat-ref}/filebeat-modules.html[{filebeat} modules]) are ECS-compliant, which means data they ship to {elastic-sec} will automatically populate the relevant ECS fields. If you plan to use a custom implementation to map your data to ECS fields (see {ecs-ref}/ecs-converting.html[how to map data to ECS]), ensure the <> are populated. Ideally, all relevant ECS fields should be populated as well. +For detailed information about which ECS fields can appear in documents generated by {elastic-endpoint}, refer to the https://github.com/elastic/endpoint-package/tree/main/custom_documentation/doc/endpoint[Endpoint event documentation]. + [float] [[siem-always-required-fields]] == Always required fields