Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
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
9 changes: 9 additions & 0 deletions docs/reference/ecs-allowed-values-entity-type.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,8 @@ This field is an array. This allows proper categorization of entities that may f
* [service](#ecs-entity-type-service)
* [session](#ecs-entity-type-session)
* [user](#ecs-entity-type-user)
* [cloud](#ecs-entity-type-cloud)
* [orchestrator](#ecs-entity-type-orchestrator)


## application [ecs-entity-type-application]
Expand Down Expand Up @@ -78,3 +80,10 @@ Represents a user session or connection session. This includes user login sessio

Represents a user account or identity. This includes human users, service accounts, system accounts, and other identity entities that can interact with systems, applications, or services. Users may have various roles, permissions, and attributes associated with their identity.


## cloud [ecs-entity-type-cloud]
Represents a cloud or infrastructure. This includes cloud providers and their services (such as AWS EC2), and is used to identify or correlate resources, entities, and activities across accounts or multi-cloud environments.


## orchestrator [ecs-entity-type-orchestrator]
Represents an orchestration system or orchestrator component. This includes container orchestrators like Kubernetes, Docker Swarm, and other systems responsible for automating the deployment, management, scaling, and networking of containers or workloads.
11 changes: 10 additions & 1 deletion docs/reference/ecs-entity.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,5 +38,14 @@ The `entity` fields are expected to be nested at:
* `orchestrator.entity`
* `service.entity`
* `user.entity`
* `entity.target`

Note also that the `entity` fields are not expected to be used directly at the root of the events.

Note also that the `entity` fields may be used directly at the root of the events.


### Field sets that can be nested under User [ecs-entity-nestings]

| Location | Field Set | Description |
| --- | --- | --- |
| `entity.target.*` | [entity](/reference/ecs-entity.md) | Targeted entity of action taken. |
Loading