-
Notifications
You must be signed in to change notification settings - Fork 418
/
fields.ecs.yml
13794 lines (13200 loc) · 484 KB
/
fields.ecs.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# WARNING! Do not edit this file directly, it was generated by the ECS project,
# based on ECS version 9.0.0-dev.
# Please visit https://github.com/elastic/ecs to suggest changes to ECS fields.
- key: ecs
title: ECS
description: ECS Fields.
fields:
- name: '@timestamp'
level: core
required: true
type: date
description: 'Date/time when the event originated.
This is the date/time extracted from the event, typically representing when
the event was generated by the source.
If the event source has no original timestamp, this value is typically populated
by the first time the event was received by the pipeline.
Required field for all events.'
example: '2016-05-23T08:05:34.853Z'
default_field: true
- name: labels
level: core
type: object
object_type: keyword
description: 'Custom key/value pairs.
Can be used to add meta information to events. Should not contain nested objects.
All values are stored as keyword.
Example: `docker` and `k8s` labels.'
example: '{"application": "foo-bar", "env": "production"}'
default_field: true
- name: message
level: core
type: match_only_text
description: 'For log events the message field contains the log message, optimized
for viewing in a log viewer.
For structured logs without an original message field, other fields can be concatenated
to form a human-readable summary of the event.
If multiple messages exist, they can be combined into one message.'
example: Hello World
default_field: true
- name: tags
level: core
type: keyword
ignore_above: 1024
description: List of keywords used to tag each event.
example: '["production", "env2"]'
default_field: true
- name: agent
title: Agent
group: 2
description: 'The agent fields contain the data about the software entity, if
any, that collects, detects, or observes events on a host, or takes measurements
on a host.
Examples include Beats. Agents may also run on observers. ECS agent.* fields
shall be populated with details of the agent running on the host or observer
where the event happened or the measurement was taken.'
footnote: 'Examples: In the case of Beats for logs, the agent.name is filebeat.
For APM, it is the agent running in the app/service. The agent information does
not change if data is sent through queuing systems like Kafka, Redis, or processing
systems such as Logstash or APM Server.'
type: group
default_field: true
fields:
- name: build.original
level: core
type: keyword
ignore_above: 1024
description: 'Extended build information for the agent.
This field is intended to contain any build information that a data source
may provide, no specific formatting is required.'
example: metricbeat version 7.6.0 (amd64), libbeat 7.6.0 [6a23e8f8f30f5001ba344e4e54d8d9cb82cb107c
built 2020-02-05 23:10:10 +0000 UTC]
default_field: false
- name: ephemeral_id
level: extended
type: keyword
ignore_above: 1024
description: 'Ephemeral identifier of this agent (if one exists).
This id normally changes across restarts, but `agent.id` does not.'
example: 8a4f500f
- name: id
level: core
type: keyword
ignore_above: 1024
description: 'Unique identifier of this agent (if one exists).
Example: For Beats this would be beat.id.'
example: 8a4f500d
- name: name
level: core
type: keyword
ignore_above: 1024
description: 'Custom name of the agent.
This is a name that can be given to an agent. This can be helpful if for example
two Filebeat instances are running on the same host but a human readable separation
is needed on which Filebeat instance data is coming from.'
example: foo
- name: type
level: core
type: keyword
ignore_above: 1024
description: 'Type of the agent.
The agent type always stays the same and should be given by the agent used.
In case of Filebeat the agent would always be Filebeat also if two Filebeat
instances are run on the same machine.'
example: filebeat
- name: version
level: core
type: keyword
ignore_above: 1024
description: Version of the agent.
example: 6.0.0-rc2
- name: client
title: Client
group: 2
description: 'A client is defined as the initiator of a network connection for
events regarding sessions, connections, or bidirectional flow records.
For TCP events, the client is the initiator of the TCP connection that sends
the SYN packet(s). For other protocols, the client is generally the initiator
or requestor in the network transaction. Some systems use the term "originator"
to refer the client in TCP connections. The client fields describe details about
the system acting as the client in the network event. Client fields are usually
populated in conjunction with server fields. Client fields are generally not
populated for packet-level events.
Client / server representations can add semantic context to an exchange, which
is helpful to visualize the data in certain situations. If your context falls
in that category, you should still ensure that source and destination are filled
appropriately.'
type: group
default_field: true
fields:
- name: address
level: extended
type: keyword
ignore_above: 1024
description: 'Some event client addresses are defined ambiguously. The event
will sometimes list an IP, a domain or a unix socket. You should always store
the raw address in the `.address` field.
Then it should be duplicated to `.ip` or `.domain`, depending on which one
it is.'
- name: as.number
level: extended
type: long
description: Unique number allocated to the autonomous system. The autonomous
system number (ASN) uniquely identifies each network on the Internet.
example: 15169
- name: as.organization.name
level: extended
type: keyword
ignore_above: 1024
multi_fields:
- name: text
type: match_only_text
default_field: false
description: Organization name.
example: Google LLC
- name: bytes
level: core
type: long
format: bytes
description: Bytes sent from the client to the server.
example: 184
- name: domain
level: core
type: keyword
ignore_above: 1024
description: 'The domain name of the client system.
This value may be a host name, a fully qualified domain name, or another host
naming format. The value may derive from the original event or be added from
enrichment.'
example: foo.example.com
- name: geo.city_name
level: core
type: keyword
ignore_above: 1024
description: City name.
example: Montreal
- name: geo.continent_code
level: core
type: keyword
ignore_above: 1024
description: Two-letter code representing continent's name.
example: NA
default_field: false
- name: geo.continent_name
level: core
type: keyword
ignore_above: 1024
description: Name of the continent.
example: North America
- name: geo.country_iso_code
level: core
type: keyword
ignore_above: 1024
description: Country ISO code.
example: CA
- name: geo.country_name
level: core
type: keyword
ignore_above: 1024
description: Country name.
example: Canada
- name: geo.location
level: core
type: geo_point
description: Longitude and latitude.
example: '{ "lon": -73.614830, "lat": 45.505918 }'
- name: geo.name
level: extended
type: keyword
ignore_above: 1024
description: 'User-defined description of a location, at the level of granularity
they care about.
Could be the name of their data centers, the floor number, if this describes
a local physical entity, city names.
Not typically used in automated geolocation.'
example: boston-dc
- name: geo.postal_code
level: core
type: keyword
ignore_above: 1024
description: 'Postal code associated with the location.
Values appropriate for this field may also be known as a postcode or ZIP code
and will vary widely from country to country.'
example: 94040
default_field: false
- name: geo.region_iso_code
level: core
type: keyword
ignore_above: 1024
description: Region ISO code.
example: CA-QC
- name: geo.region_name
level: core
type: keyword
ignore_above: 1024
description: Region name.
example: Quebec
- name: geo.timezone
level: core
type: keyword
ignore_above: 1024
description: The time zone of the location, such as IANA time zone name.
example: America/Argentina/Buenos_Aires
default_field: false
- name: ip
level: core
type: ip
description: IP address of the client (IPv4 or IPv6).
- name: mac
level: core
type: keyword
ignore_above: 1024
description: 'MAC address of the client.
The notation format from RFC 7042 is suggested: Each octet (that is, 8-bit
byte) is represented by two [uppercase] hexadecimal digits giving the value
of the octet as an unsigned integer. Successive octets are separated by a
hyphen.'
example: 00-00-5E-00-53-23
pattern: ^[A-F0-9]{2}(-[A-F0-9]{2}){5,}$
- name: nat.ip
level: extended
type: ip
description: 'Translated IP of source based NAT sessions (e.g. internal client
to internet).
Typically connections traversing load balancers, firewalls, or routers.'
- name: nat.port
level: extended
type: long
format: string
description: 'Translated port of source based NAT sessions (e.g. internal client
to internet).
Typically connections traversing load balancers, firewalls, or routers.'
- name: packets
level: core
type: long
description: Packets sent from the client to the server.
example: 12
- name: port
level: core
type: long
format: string
description: Port of the client.
- name: registered_domain
level: extended
type: keyword
ignore_above: 1024
description: 'The highest registered client domain, stripped of the subdomain.
For example, the registered domain for "foo.example.com" is "example.com".
This value can be determined precisely with a list like the public suffix
list (http://publicsuffix.org). Trying to approximate this by simply taking
the last two labels will not work well for TLDs such as "co.uk".'
example: example.com
- name: subdomain
level: extended
type: keyword
ignore_above: 1024
description: 'The subdomain portion of a fully qualified domain name includes
all of the names except the host name under the registered_domain. In a partially
qualified domain, or if the the qualification level of the full name cannot
be determined, subdomain contains all of the names below the registered domain.
For example the subdomain portion of "www.east.mydomain.co.uk" is "east".
If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com",
the subdomain field should contain "sub2.sub1", with no trailing period.'
example: east
default_field: false
- name: top_level_domain
level: extended
type: keyword
ignore_above: 1024
description: 'The effective top level domain (eTLD), also known as the domain
suffix, is the last part of the domain name. For example, the top level domain
for example.com is "com".
This value can be determined precisely with a list like the public suffix
list (http://publicsuffix.org). Trying to approximate this by simply taking
the last label will not work well for effective TLDs such as "co.uk".'
example: co.uk
- name: user.domain
level: extended
type: keyword
ignore_above: 1024
description: 'Name of the directory the user is a member of.
For example, an LDAP or Active Directory domain name.'
- name: user.email
level: extended
type: keyword
ignore_above: 1024
description: User email address.
- name: user.full_name
level: extended
type: keyword
ignore_above: 1024
multi_fields:
- name: text
type: match_only_text
default_field: false
description: User's full name, if available.
example: Albert Einstein
- name: user.group.domain
level: extended
type: keyword
ignore_above: 1024
description: 'Name of the directory the group is a member of.
For example, an LDAP or Active Directory domain name.'
- name: user.group.id
level: extended
type: keyword
ignore_above: 1024
description: Unique identifier for the group on the system/platform.
- name: user.group.name
level: extended
type: keyword
ignore_above: 1024
description: Name of the group.
- name: user.hash
level: extended
type: keyword
ignore_above: 1024
description: 'Unique user hash to correlate information for a user in anonymized
form.
Useful if `user.id` or `user.name` contain confidential information and cannot
be used.'
- name: user.id
level: core
type: keyword
ignore_above: 1024
description: Unique identifier of the user.
example: S-1-5-21-202424912787-2692429404-2351956786-1000
- name: user.name
level: core
type: keyword
ignore_above: 1024
multi_fields:
- name: text
type: match_only_text
default_field: false
description: Short name or login of the user.
example: a.einstein
- name: user.roles
level: extended
type: keyword
ignore_above: 1024
description: Array of user roles at the time of the event.
example: '["kibana_admin", "reporting_user"]'
default_field: false
- name: cloud
title: Cloud
group: 2
description: Fields related to the cloud or infrastructure the events are coming
from.
footnote: 'Examples: If Metricbeat is running on an EC2 host and fetches data
from its host, the cloud info contains the data about this machine. If Metricbeat
runs on a remote machine outside the cloud and fetches data from a service running
in the cloud, the field contains cloud data from the machine the service is
running on.
The cloud fields may be self-nested under cloud.origin.* and cloud.target.*
to describe origin or target service''s cloud information in the context of
incoming or outgoing requests, respectively. However, the fieldsets cloud.origin.*
and cloud.target.* must not be confused with the root cloud fieldset that is
used to describe the cloud context of the actual service under observation.
The fieldset cloud.origin.* may only be used in the context of incoming requests
or events to provide the originating service''s cloud information. The fieldset
cloud.target.* may only be used in the context of outgoing requests or events
to describe the target service''s cloud information.'
type: group
default_field: true
fields:
- name: account.id
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud account or organization id used to identify different
entities in a multi-tenant environment.
Examples: AWS account id, Google Cloud ORG Id, or other unique identifier.'
example: 666777888999
- name: account.name
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud account name or alias used to identify different entities
in a multi-tenant environment.
Examples: AWS account name, Google Cloud ORG display name.'
example: elastic-dev
default_field: false
- name: availability_zone
level: extended
type: keyword
ignore_above: 1024
description: Availability zone in which this host, resource, or service is located.
example: us-east-1c
- name: instance.id
level: extended
type: keyword
ignore_above: 1024
description: Instance ID of the host machine.
example: i-1234567890abcdef0
- name: instance.name
level: extended
type: keyword
ignore_above: 1024
description: Instance name of the host machine.
- name: machine.type
level: extended
type: keyword
ignore_above: 1024
description: Machine type of the host machine.
example: t2.medium
- name: origin.account.id
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud account or organization id used to identify different
entities in a multi-tenant environment.
Examples: AWS account id, Google Cloud ORG Id, or other unique identifier.'
example: 666777888999
default_field: false
- name: origin.account.name
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud account name or alias used to identify different entities
in a multi-tenant environment.
Examples: AWS account name, Google Cloud ORG display name.'
example: elastic-dev
default_field: false
- name: origin.availability_zone
level: extended
type: keyword
ignore_above: 1024
description: Availability zone in which this host, resource, or service is located.
example: us-east-1c
default_field: false
- name: origin.instance.id
level: extended
type: keyword
ignore_above: 1024
description: Instance ID of the host machine.
example: i-1234567890abcdef0
default_field: false
- name: origin.instance.name
level: extended
type: keyword
ignore_above: 1024
description: Instance name of the host machine.
default_field: false
- name: origin.machine.type
level: extended
type: keyword
ignore_above: 1024
description: Machine type of the host machine.
example: t2.medium
default_field: false
- name: origin.project.id
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud project identifier.
Examples: Google Cloud Project id, Azure Project id.'
example: my-project
default_field: false
- name: origin.project.name
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud project name.
Examples: Google Cloud Project name, Azure Project name.'
example: my project
default_field: false
- name: origin.provider
level: extended
type: keyword
ignore_above: 1024
description: Name of the cloud provider. Example values are aws, azure, gcp,
or digitalocean.
example: aws
default_field: false
- name: origin.region
level: extended
type: keyword
ignore_above: 1024
description: Region in which this host, resource, or service is located.
example: us-east-1
default_field: false
- name: origin.service.name
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud service name is intended to distinguish services running
on different platforms within a provider, eg AWS EC2 vs Lambda, GCP GCE vs
App Engine, Azure VM vs App Server.
Examples: app engine, app service, cloud run, fargate, lambda.'
example: lambda
default_field: false
- name: project.id
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud project identifier.
Examples: Google Cloud Project id, Azure Project id.'
example: my-project
default_field: false
- name: project.name
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud project name.
Examples: Google Cloud Project name, Azure Project name.'
example: my project
default_field: false
- name: provider
level: extended
type: keyword
ignore_above: 1024
description: Name of the cloud provider. Example values are aws, azure, gcp,
or digitalocean.
example: aws
- name: region
level: extended
type: keyword
ignore_above: 1024
description: Region in which this host, resource, or service is located.
example: us-east-1
- name: service.name
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud service name is intended to distinguish services running
on different platforms within a provider, eg AWS EC2 vs Lambda, GCP GCE vs
App Engine, Azure VM vs App Server.
Examples: app engine, app service, cloud run, fargate, lambda.'
example: lambda
default_field: false
- name: target.account.id
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud account or organization id used to identify different
entities in a multi-tenant environment.
Examples: AWS account id, Google Cloud ORG Id, or other unique identifier.'
example: 666777888999
default_field: false
- name: target.account.name
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud account name or alias used to identify different entities
in a multi-tenant environment.
Examples: AWS account name, Google Cloud ORG display name.'
example: elastic-dev
default_field: false
- name: target.availability_zone
level: extended
type: keyword
ignore_above: 1024
description: Availability zone in which this host, resource, or service is located.
example: us-east-1c
default_field: false
- name: target.instance.id
level: extended
type: keyword
ignore_above: 1024
description: Instance ID of the host machine.
example: i-1234567890abcdef0
default_field: false
- name: target.instance.name
level: extended
type: keyword
ignore_above: 1024
description: Instance name of the host machine.
default_field: false
- name: target.machine.type
level: extended
type: keyword
ignore_above: 1024
description: Machine type of the host machine.
example: t2.medium
default_field: false
- name: target.project.id
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud project identifier.
Examples: Google Cloud Project id, Azure Project id.'
example: my-project
default_field: false
- name: target.project.name
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud project name.
Examples: Google Cloud Project name, Azure Project name.'
example: my project
default_field: false
- name: target.provider
level: extended
type: keyword
ignore_above: 1024
description: Name of the cloud provider. Example values are aws, azure, gcp,
or digitalocean.
example: aws
default_field: false
- name: target.region
level: extended
type: keyword
ignore_above: 1024
description: Region in which this host, resource, or service is located.
example: us-east-1
default_field: false
- name: target.service.name
level: extended
type: keyword
ignore_above: 1024
description: 'The cloud service name is intended to distinguish services running
on different platforms within a provider, eg AWS EC2 vs Lambda, GCP GCE vs
App Engine, Azure VM vs App Server.
Examples: app engine, app service, cloud run, fargate, lambda.'
example: lambda
default_field: false
- name: container
title: Container
group: 2
description: 'Container fields are used for meta information about the specific
container that is the source of information.
These fields help correlate data based containers from any runtime.'
type: group
default_field: true
fields:
- name: cpu.usage
level: extended
type: scaled_float
description: 'Percent CPU used which is normalized by the number of CPU cores
and it ranges from 0 to 1. Scaling factor: 1000.'
scaling_factor: 1000
default_field: false
- name: disk.read.bytes
level: extended
type: long
description: The total number of bytes (gauge) read successfully (aggregated
from all disks) since the last metric collection.
default_field: false
- name: disk.write.bytes
level: extended
type: long
description: The total number of bytes (gauge) written successfully (aggregated
from all disks) since the last metric collection.
default_field: false
- name: id
level: core
type: keyword
ignore_above: 1024
description: Unique container id.
- name: image.hash.all
level: extended
type: keyword
ignore_above: 1024
description: 'An array of digests of the image the container was built on. Each
digest consists of the hash algorithm and value in this format: `algorithm:value`.
Algorithm names should align with the field names in the ECS hash field set.'
example: '[sha256:f8fefc80e3273dc756f288a63945820d6476ad64883892c771b5e2ece6bf1b26]'
default_field: false
- name: image.name
level: extended
type: keyword
ignore_above: 1024
description: Name of the image the container was built on.
- name: image.tag
level: extended
type: keyword
ignore_above: 1024
description: Container image tags.
- name: labels
level: extended
type: object
object_type: keyword
description: Image labels.
- name: memory.usage
level: extended
type: scaled_float
description: 'Memory usage percentage and it ranges from 0 to 1. Scaling factor:
1000.'
scaling_factor: 1000
default_field: false
- name: name
level: extended
type: keyword
ignore_above: 1024
description: Container name.
- name: network.egress.bytes
level: extended
type: long
description: The number of bytes (gauge) sent out on all network interfaces
by the container since the last metric collection.
default_field: false
- name: network.ingress.bytes
level: extended
type: long
description: The number of bytes received (gauge) on all network interfaces
by the container since the last metric collection.
default_field: false
- name: runtime
level: extended
type: keyword
ignore_above: 1024
description: Runtime managing this container.
example: docker
- name: security_context.privileged
level: extended
type: boolean
description: Indicates whether the container is running in privileged mode.
default_field: false
- name: data_stream
title: Data Stream
group: 2
description: 'The data_stream fields take part in defining the new data stream
naming scheme.
In the new data stream naming scheme the value of the data stream fields combine
to the name of the actual data stream in the following manner: `{data_stream.type}-{data_stream.dataset}-{data_stream.namespace}`.
This means the fields can only contain characters that are valid as part of
names of data streams. More details about this can be found in this https://www.elastic.co/blog/an-introduction-to-the-elastic-data-stream-naming-scheme[blog
post].
An Elasticsearch data stream consists of one or more backing indices, and a
data stream name forms part of the backing indices names. Due to this convention,
data streams must also follow index naming restrictions. For example, data stream
names cannot include `\`, `/`, `*`, `?`, `"`, `<`, `>`, `|`, ` ` (space character),
`,`, or `#`. Please see the Elasticsearch reference for additional https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-index.html#indices-create-api-path-params[restrictions].'
type: group
default_field: true
fields:
- name: dataset
level: extended
type: constant_keyword
description: "The field can contain anything that makes sense to signify the\
\ source of the data.\nExamples include `nginx.access`, `prometheus`, `endpoint`\
\ etc. For data streams that otherwise fit, but that do not have dataset set\
\ we use the value \"generic\" for the dataset value. `event.dataset` should\
\ have the same value as `data_stream.dataset`.\nBeyond the Elasticsearch\
\ data stream naming criteria noted above, the `dataset` value has additional\
\ restrictions:\n * Must not contain `-`\n * No longer than 100 characters"
example: nginx.access
default_field: false
- name: namespace
level: extended
type: constant_keyword
description: "A user defined namespace. Namespaces are useful to allow grouping\
\ of data.\nMany users already organize their indices this way, and the data\
\ stream naming scheme now provides this best practice as a default. Many\
\ users will populate this field with `default`. If no value is used, it falls\
\ back to `default`.\nBeyond the Elasticsearch index naming criteria noted\
\ above, `namespace` value has the additional restrictions:\n * Must not\
\ contain `-`\n * No longer than 100 characters"
example: production
default_field: false
- name: type
level: extended
type: constant_keyword
description: 'An overarching type for the data stream.
Currently allowed values are "logs" and "metrics". We expect to also add "traces"
and "synthetics" in the near future.'
example: logs
default_field: false
- name: destination
title: Destination
group: 2
description: 'Destination fields capture details about the receiver of a network
exchange/packet. These fields are populated from a network event, packet, or
other event containing details of a network transaction.
Destination fields are usually populated in conjunction with source fields.
The source and destination fields are considered the baseline and should always
be filled if an event contains source and destination details from a network
transaction. If the event also contains identification of the client and server
roles, then the client and server fields should also be populated.'
type: group
default_field: true
fields:
- name: address
level: extended
type: keyword
ignore_above: 1024
description: 'Some event destination addresses are defined ambiguously. The
event will sometimes list an IP, a domain or a unix socket. You should always
store the raw address in the `.address` field.
Then it should be duplicated to `.ip` or `.domain`, depending on which one
it is.'
- name: as.number
level: extended
type: long
description: Unique number allocated to the autonomous system. The autonomous
system number (ASN) uniquely identifies each network on the Internet.
example: 15169
- name: as.organization.name
level: extended
type: keyword
ignore_above: 1024
multi_fields:
- name: text
type: match_only_text
default_field: false
description: Organization name.
example: Google LLC
- name: bytes
level: core
type: long
format: bytes
description: Bytes sent from the destination to the source.
example: 184
- name: domain
level: core
type: keyword
ignore_above: 1024
description: 'The domain name of the destination system.
This value may be a host name, a fully qualified domain name, or another host
naming format. The value may derive from the original event or be added from
enrichment.'
example: foo.example.com
- name: geo.city_name
level: core
type: keyword
ignore_above: 1024
description: City name.
example: Montreal
- name: geo.continent_code
level: core
type: keyword
ignore_above: 1024
description: Two-letter code representing continent's name.
example: NA
default_field: false
- name: geo.continent_name
level: core
type: keyword
ignore_above: 1024
description: Name of the continent.
example: North America
- name: geo.country_iso_code
level: core
type: keyword
ignore_above: 1024
description: Country ISO code.
example: CA
- name: geo.country_name
level: core
type: keyword
ignore_above: 1024
description: Country name.
example: Canada
- name: geo.location
level: core
type: geo_point
description: Longitude and latitude.
example: '{ "lon": -73.614830, "lat": 45.505918 }'
- name: geo.name
level: extended
type: keyword
ignore_above: 1024
description: 'User-defined description of a location, at the level of granularity
they care about.
Could be the name of their data centers, the floor number, if this describes
a local physical entity, city names.
Not typically used in automated geolocation.'
example: boston-dc
- name: geo.postal_code
level: core
type: keyword
ignore_above: 1024
description: 'Postal code associated with the location.
Values appropriate for this field may also be known as a postcode or ZIP code
and will vary widely from country to country.'
example: 94040
default_field: false
- name: geo.region_iso_code
level: core
type: keyword
ignore_above: 1024
description: Region ISO code.
example: CA-QC
- name: geo.region_name
level: core
type: keyword
ignore_above: 1024
description: Region name.
example: Quebec
- name: geo.timezone
level: core
type: keyword
ignore_above: 1024
description: The time zone of the location, such as IANA time zone name.
example: America/Argentina/Buenos_Aires
default_field: false
- name: ip
level: core
type: ip
description: IP address of the destination (IPv4 or IPv6).
- name: mac
level: core
type: keyword
ignore_above: 1024
description: 'MAC address of the destination.
The notation format from RFC 7042 is suggested: Each octet (that is, 8-bit
byte) is represented by two [uppercase] hexadecimal digits giving the value
of the octet as an unsigned integer. Successive octets are separated by a
hyphen.'
example: 00-00-5E-00-53-23
pattern: ^[A-F0-9]{2}(-[A-F0-9]{2}){5,}$
- name: nat.ip