Using ECS
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
ECS fields follow a series of guidelines, to ensure a consistent and predictable feel, across various use cases.
If you're new to ECS and would like an introduction on implementing and using the schema, check out the Getting started guide.
Whether you're trying to recall a field name, implementing a solution that follows ECS, or proposing a change to the schema, the Guidelines and best practices section will help get you there.
Design principles are a set of considerations used to help guide the ECS project.
If you're wondering how to best capture event details that don't map to existing ECS fields, head over to Custom fields.