forked from elastic/ecs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
geo.yml
83 lines (72 loc) · 1.81 KB
/
geo.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
---
- name: geo
title: Geo
group: 2
short: Fields describing a location.
description: >
Geo fields can carry data about a specific location related to an event.
This geolocation information can be derived from techniques such as Geo IP,
or be user-supplied.
reusable:
top_level: false
expected:
- client
- destination
- observer
- host
- server
- source
type: group
fields:
- name: location
level: core
type: geo_point
description: >
Longitude and latitude.
example: '{ "lon": -73.614830, "lat": 45.505918 }'
- name: continent_name
level: core
type: keyword
description: >
Name of the continent.
example: North America
- name: country_name
level: core
type: keyword
description: >
Country name.
example: Canada
- name: region_name
level: core
type: keyword
description: >
Region name.
example: Quebec
- name: city_name
level: core
type: keyword
description: >
City name.
example: Montreal
- name: country_iso_code
level: core
type: keyword
description: >
Country ISO code.
example: CA
- name: region_iso_code
level: core
type: keyword
description: >
Region ISO code.
example: CA-QC
- name: name
level: extended
type: keyword
short: User-defined description of a location.
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