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

Add one new OS field with predictable set of values #1110

Closed
webmat opened this issue Nov 11, 2020 · 1 comment · Fixed by #1111
Closed

Add one new OS field with predictable set of values #1110

webmat opened this issue Nov 11, 2020 · 1 comment · Fixed by #1111
Labels
1.8.0 enhancement New feature or request

Comments

@webmat
Copy link
Contributor

webmat commented Nov 11, 2020

Summary

The current OS fields in ECS were inherited from Beats, and didn't come with very strong guidance on how to populate them. This has led to a few of the fields being used inconsistently across data sources (mainly os.platform, os.family and to a lesser extent os.name, os.full).

This in turn means it's difficult to reliably filter for "Linux" events, for example. Currently some sources put "Linux" in one of the fields, some other sources put distro details in some of these fields (e.g. rhel / redhat) with no trace of the word Linux in sight 🙂

Motivation:

We want to make it easy to filter for Windows, Linux, Unix and MacOS events. They're broadly speaking the main commercial platforms out there.

Detailed Design:

The proposal is to add a single new field that will have allowed values that need to be used.

Field name: os.type
Field type: keyword
Allowed values (lowercase):

  • windows
  • linux
  • unix
  • macos

Note: This issue is not about revamping the guidance on the OS field set; although this would be worth doing, in preparation for the next major release.

@webmat
Copy link
Contributor Author

webmat commented Nov 11, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.8.0 enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant