Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.x](backport #4439) Port #4340 to stateful: Update EEM to reflect Inventory #4469

Merged
merged 1 commit into from
Nov 2, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions docs/en/observability/elastic-entity-model.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -18,15 +18,14 @@ The concept of an entity is important as a means to unify observability signals

[NOTE]
====
* The Elastic Entity Model currently supports the <<new-experience-services,new service inventory experience>> limited to service-based entities (as identified by `service.name`) located in data identified by `logs-*` and `filebeat*` index patterns
* During Technical Preview, Entity Discovery Framework components are not enabled by default
* The Elastic Entity Model currently supports the <<inventory,new Inventory experience>> limited to service, host, and container entities.
* During Technical Preview, Entity Discovery Framework components are not enabled by default.
====

[discrete]
== Enable the Elastic Entity Model

During Technical Preview,
the Elastic Entity Model is enabled when you turn on the entity-centric service inventory described in <<new-experience-services>>.
You can enable the Elastic Entity Model from the new <<inventory,Inventory>>. If already enabled, you will not be prompted to enable the Elastic Entity Model.

The following {es} privileges are required:

Expand Down