Skip to content

Commit 3dee0fb

Browse files
Add event.provider to API events (#631)
1 parent acece60 commit 3dee0fb

File tree

3 files changed

+24
-0
lines changed

3 files changed

+24
-0
lines changed

custom_subsets/elastic_endpoint/api/api.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,7 @@ fields:
3838
hash: {}
3939
id: {}
4040
ingested: {}
41+
provider: {}
4142
outcome: {}
4243
start: {}
4344
type: {}

package/endpoint/data_stream/api/fields/fields.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1068,6 +1068,14 @@
10681068
10691069
Further note that not all events will have an associated outcome. For example, this field is generally not populated for metric events, events with `event.type:info`, or any events for which an outcome does not make logical sense.'
10701070
example: success
1071+
- name: provider
1072+
level: extended
1073+
type: keyword
1074+
ignore_above: 1024
1075+
description: 'Source of the event.
1076+
1077+
Event transports such as Syslog or the Windows Event Log typically mention the source of an event. It can be the name of the software that generated the event (e.g. Sysmon, httpd), or of a subsystem of the operating system (kernel, Microsoft-Windows-Security-Auditing).'
1078+
example: kernel
10711079
- name: start
10721080
level: extended
10731081
type: date

schemas/v1/api/api.yaml

Lines changed: 15 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)