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

add enabled_features to the heartbeat document #399

Merged
merged 1 commit into from
Aug 4, 2023
Merged
Show file tree
Hide file tree
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

This file was deleted.

5 changes: 5 additions & 0 deletions custom_schemas/custom_endpoint.yml
Original file line number Diff line number Diff line change
Expand Up @@ -1038,6 +1038,11 @@
type: boolean
description: Current network isolation state of the host

- name: state.enabled_features
level: custom
type: keyword
description: High level summary of policy features actively in use

- name: capabilities
level: custom
type: keyword
Expand Down
5 changes: 5 additions & 0 deletions custom_subsets/elastic_endpoint/heartbeat/heartbeat.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,8 @@ fields:
event:
fields:
ingested: {}
Endpoint:
fields:
state:
fields:
enabled_features: {}
18 changes: 18 additions & 0 deletions package/endpoint/data_stream/heartbeat/fields/fields.yml
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,24 @@
If multiple messages exist, they can be combined into one message.'
example: Hello World
default_field: true
- name: Endpoint
title: Endpoint
group: 2
description: Fields describing the state of the Elastic Endpoint when an event occurs.
type: group
default_field: true
fields:
- name: state
level: custom
type: object
description: Represents the current state of a non-policy setting These fields reflect the current status of a field, which may differ from what it is configured to be (see Endpoint.configuration)
default_field: false
- name: state.enabled_features
level: custom
type: keyword
ignore_above: 1024
description: High level summary of policy features actively in use
default_field: false
- name: agent
title: Agent
group: 2
Expand Down
12 changes: 12 additions & 0 deletions package/endpoint/data_stream/heartbeat/sample_event.json
Original file line number Diff line number Diff line change
Expand Up @@ -11,5 +11,17 @@
"message": "Endpoint heartbeat",
"event": {
"ingested": "2023-07-18T20:40:09.279939Z"
},
"Endpoint": {
"state": {
"enabled_features": [
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@joeypoon what do you think of this exact location? Endpoint.state.host_isolation=true|false already exists. It felt like this belonged along side it conceptually.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make sense to me 👍

"malware",
"ransomware",
"attack_surface_reduction",
"memory_threat",
"malicious_behavior",
"events"
]
}
}
}

This file was deleted.

23 changes: 23 additions & 0 deletions schemas/v1/heartbeat/heartbeat.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.