elastic / elastic/ecs

ECS Safety template for field types needed, so different versions can be supported

Open
#548 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.1k
Forks
455
Avg merge
17h 8m
Merged PRs (30d)
5

Description

So that new filebeat versions that send into our 701 ECS template do NOT break our kibana index patterns mapped to filebeat-7.0.1*, I'd like to have a base template that factors in all field types, per the naming standards.

i.e,
everying ending in ip is geo
and all other conventions for naming standards (which I cannot find)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.