Releases: elastic/ecs
ECS 8.5.0-rc1
ECS Release Candidate
Schema Changes
Added
- Adding
risk.*fields as experimental. #1994, #2010 - Adding
process.io.*as beta fields. #1956, #2031 - Adding
process.tty.rowsandprocess.tty.columnsas beta fields. #2031 - Changed
process.env_varsfield type to be an array of keywords. #2038 process.attested_userandprocess.attested_groupsas beta fields. #2050- Added
risk.*fieldset to beta. #2051
Improvements
- Advances
threat.enrichments.indicatorto GA. #1928 - Added
iosandandroidas valid values foros.type#1999
Tooling and Artifact Changes
Bugfixes
ECS 8.4.0
What's new in ECS 8.4
New field attribute expected_values
ECS schema field definitions will now support an attribute to provide a consistent location to capture a list of expected values.
Schema Changes
Added
Tooling and Artifact Changes
Added
- Introduce
expected_valuesattribute. #1952
Improvements
- Additional type annotations. #1950
ECS 8.4.0-rc1
ECS 8.3.1
ECS 8.3.0
What's new in ECS 8.3
GA additions to the schema
The container.* metrics fieldset
Proposed in RFC 0025, this release introduces the container.* field set as GA. These additional container metric fields capture container CPU, memory, disk and network performance information.
Pattern attribute for .mac fields
ECS sets the pattern attribute for the .mac address fields. The regex value is based on the format suggested in IETF RFC 7042.
Schema Changes
Added
- Added
patternattribute to.macfields. #1871 - Add
orchestrator.cluster.id#1875 - Add
orchestrator.resource.id#1878 - Add
orchestrator.resource.parent.type#1889 - Add
orchestrator.resource.ip#1889 - Add
container.image.hash.all#1889 - Add
service.node.role#1916 - Advanced
container.*metric fields to GA. #1927
Important
After adding service.node.role, it was realized that we intend for this field to have multiple values, and therefore we will be removing role and replacing with roles at the earliest opportunity. Please do not use service.node.role.
ECS 8.2.1
ECS 8.2.0
What's new in ECS 8.2
Beta additions to the schema
The linux event model fields
Proposed in RFC 0030, this release introduces a variety of new beta fields that model a linux event model in order to drive Session view in Kibana.
The container.* metrics fieldset
Proposed in RFC 0025, this release introduces a beta container.* field set. These additional container metric fields capture container CPU, memory, disk and network performance information.
Tooling improvements
In 8.2, ECS has introduced a new optional field definition attribute: pattern. The pattern attribute holds a regular expression (regex) which expresses the expected constraint on a string field's value. This field is intended to be utilized in automated testing for validation of the values populating ECS fields.
Changelog
Schema Changes
Added
- Add beta
container.*metric fields. #1789 - Add six new syslog fields to
log.syslog.*. #1793 - Added
faas.id,faas.nameandfaas.versionfields as beta. #1796 - Added linux event model beta fields and reuses to support RFC 0030. #1842, #1847, #1884
- Added
threat.feed.dashboard_id,threat.feed.description,threat.feed.name,threat.feed.referencefields. #1844
Improvements
Tooling and Artifact Changes
Added
- Adding optional field attribute,
pattern. #1834 - Added support for re-using a fieldset as an array. #1838
- Added
--force-docsoption to generator. #1879
Improvements
ECS 8.1.0
What's new in ECS 8.1
The email.* field set
Proposed in RFC 0010, this release introduces a beta email.* field set. These fields capture event details from email message headers, bodies, and attachments.
Additional hash fields
ECS 8.1 also adds three additional hash fields:
hash.sha384hash.tlshpe.pehash
These fields help align ECS with Threat Intelligence features available in the Elastic platform.
Changelog
Schema Changes
Added
- Added two new fields (sha384,tlsh) to hash schema and one field to pe schema (pehash). #1678
- Added
email.*beta field set. ##1688, #1705
Removed
- Removing
process.target.*reuses from experimental schema. #1666 - Removing RFC 0014
pe.*fields from experimental schema. #1670
Tooling and Artifact Changes
Bugfixes
- Fix invalid documentation link generation in component templates
_meta. #1728
Improvements
ECS 8.0.1
ECS 8.0.0
What's new in ECS 8.0
We're pleased to announce ECS 8.0.
Thank you to all the ECS contributors who help support the broader Elastic community.
Versioning: 1.x -> 8.0
ECS versioning now aligns with the Elastic platform beginning with 8.0.
ECS didn't follow the same release cadence as the Elastic platform when first introduced. Over time this approach added complexity for our users. For example, users might find themselves asking, "which Elastic version maps to ECS 1.6.0?". By aligning, it's clear what version of ECS maps to which Elastic platform version.
Power in simplicity. 😃
Removed fields
The following fields are removed in ECS 8.0:
| Field | Migrate to* | Reference |
|---|---|---|
log.original |
event.original |
RFC 0017 |
process.ppid |
process.parent.pid |
RFC 0022 |
host.user.* reuse |
user.* reuses |
user.* field set usage |
*Field aliases can help transition existing searches or visualizations depending on these removed fields.
New field data types
ECS 1.x introduced wildcard and match_only_text as beta field types. As of ECS 8.0, these data types are now GA.
The field types selected for ECS provide the best default experience for most users. However, some users may see interoperable data types better fitting for their use cases, and they can read more about options here.
Tooling changes
Elasticsearch generated artifacts
In 1.x, the project maintained sample index templates for two versions of Elasticsearch (6.x, 7.x). In 8.0, ECS now produces two sample template types: composable and legacy.
In composable, each ECS field set has a component template. An example component template, template.json, references each field set component template. These artifacts work with the new index templates introduced in Elasticsearch 7.8.
The legacy template will continue working with the legacy index template API.
Removed features
- Removed the already deprecated
--ossflag - Removed Go code generator to simplify the project's tooling and CI/CD pipeline.
Changelog
Schema Changes
Breaking changes
- Remove
host.user.*field reuse. #1439 - Remove deprecation notice on
http.request.method. #1443 - Migrate
log.origin.file.linefromintegertolong. #1533 - Remove
log.originalfield. #1580 - Remove
process.ppidfield. #1596
Added
Improvements
- Wildcard type field migration GA. #1582
match_only_texttype field migration GA. #1584- Threat indicator fields GA from RFC 0008. #1586
Tooling and Artifact Changes
Breaking Changes
- Removing deprecated --oss from generator #1404
- Removing use-cases directory #1405
- Remove Go code generator. #1567
- Remove template generation for ES6. #1680
- Update folder structure for generated ES artifacts. #1700, #1762
- Updated support for overridable composable settings template. #1737
Improvements
- Align input options for --include and --subset arguments #1519
- Remove remaining Go deps after removing Go code generator. #1585
- Add explicit
default_field: truefor Beats artifacts. #1633 - Reorganize docs directory structure. #1679
- Added support for
analyzerdefinitions for text fields. #1737
Bugfixes
- Fixed the
default_fieldflag for root fields in Beats generator. #1711