Event structure
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
Every event sent by Metricbeat has the same basic structure. It contains the following fields:
@timestamp- Time when the event was captured
host.hostname- Hostname of the server on which the Beat is running
agent.type- Name given to the Beat
event.module- Name of the module that the data is from
event.dataset- Name of the source dataset in the format
<module>.<metricset>
For example:
{
"@timestamp": "2016-06-22T22:05:53.291Z",
"agent": {
"type": "metricbeat"
},
"host": {
"hostname": "host.example.com",
},
"event": {
"dataset": "system.process",
"module": "system"
},
.
.
.
"type": "metricsets"
}
For more information about the exported fields, see Exported fields.