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.

Sign up for GitHub

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

RFC 0033 New Cloud related fields - stage 1 #1997

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
+37 −1
Draft

RFC 0033 New Cloud related fields - stage 1 #1997

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9567564
Add initial Stage 1 commit
legoguy1000 Jul 23, 2022
a6eb29a
Merge branch 'main' into rfc33-stage-1
legoguy1000 Jan 31, 2024
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
4 changes: 3 additions & 1 deletion rfcs/text/0033-new-cloud-fields.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# 0033: New cloud (or related) fields
<!-- Leave this ID at 0000. The ECS team will assign a unique, contiguous RFC number upon merging the initial stage of this RFC. -->

- Stage: **0 (strawperson)** <!-- Update to reflect target stage. See https://elastic.github.io/ecs/stages.html -->
- Stage: **1 (Draft)** <!-- Update to reflect target stage. See https://elastic.github.io/ecs/stages.html -->
- Date: **2022-07-22** <!-- The ECS team sets this date at merge time. This is the date of the latest stage advancement. -->

<!--
Expand Down Expand Up @@ -52,6 +52,8 @@ Possible alternatives proposed in https://github.com/elastic/ecs/issues/1725
Stage 1: Describe at a high level how this change affects fields. Include new or updated yml field definitions for all of the essential fields in this draft. While not exhaustive, the fields documented here should be comprehensive enough to deeply evaluate the technical considerations of this change. The goal here is to validate the technical details for all essential fields and to provide a basis for adding experimental field definitions to the schema. Use GitHub code blocks with yml syntax formatting, and add them to the corresponding RFC folder.
-->



<!--
Stage 2: Add or update all remaining field definitions. The list should now be exhaustive. The goal here is to validate the technical details of all remaining fields and to provide a basis for releasing these field definitions as beta in the schema. Use GitHub code blocks with yml syntax formatting, and add them to the corresponding RFC folder.
-->
Expand Down
34 changes: 34 additions & 0 deletions rfcs/text/0033/cloud.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
---
fields:
- name: network.edge_location
level: extended
type: keyword
short: Edge location identifier
description: >
The Cloud/CDN provider's edge location identifier, usually the IATA Airport code
example: LAX1

- name: cloud.image.id
level: extended
type: keyword
short: The ID of the cloud virtual machine image.
description: >
The ID of the cloud virtual machine image. AWS uses AMI.
example: ami-99999999

- name: cloud.image.name
level: extended
type: keyword
short: The friendly/display name of the cloud virtual machine image.
description: >
The friendly/display name of the cloud virtual machine image.
example: Amazon Linux AMI 2018.03

- name: cloud.instance.state
level: extended
type: keyword
short: The state of the virtual machine.
description: >
The current state of the virtual machine; pending, running, stopped, shutting-down, terminated...
example: running

Loading