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

[RFC] Proposal to define ECS-compliance - Stage 1 #1868

Merged
merged 10 commits into from
Apr 13, 2022

Conversation

ebeahan
Copy link
Member

@ebeahan ebeahan commented Mar 31, 2022

This RFC PR proposes the project establishes a definition of an "ECS-compliant" event.

Addresses #1780

Stage 1 Criteria

  • Opened pull request for this proposal
  • Identified "sponsor" at Elastic who will participate in RFC process and take ownership of the change after the process completes
  • Outlined initial field definitions - N/A
  • High-level description of examples of usage
  • High-level description of example sources of data
  • Identified potential concerns and implementation challenges/complexity
  • Subject matter experts identified and weighed in on the high level utility of these changes in the pull request
  • ECS team weighed in on appropriateness of these changes in the pull request

@ebeahan ebeahan added the RFC label Mar 31, 2022
@ebeahan ebeahan self-assigned this Mar 31, 2022
@ebeahan ebeahan requested a review from a team as a code owner March 31, 2022 21:43
@ebeahan ebeahan changed the title [RFC] Proposal to define ECS-compliance [RFC] Proposal to define ECS-compliance - Stage 1 Mar 31, 2022
Copy link
Contributor

@kgeller kgeller left a comment

Choose a reason for hiding this comment

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

LGTM

@ebeahan ebeahan merged commit ab98148 into elastic:main Apr 13, 2022
@ebeahan ebeahan deleted the rfc/ecs-compliance/stage-1 branch April 13, 2022 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants