Error 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
Metricbeat sends an error event when the service is not reachable. The error event has the same structure as the base event, but also has an error field that contains an error string. This makes it possible to check for errors across all metric events.
The following example shows an error event sent when the Apache server is not reachable:
{
"@timestamp": "2016-03-18T12:18:57.124Z",
"apache-status": {},
"beat": {
"hostname": "host.example.com",
"name": "host.example.com"
},
"error": {
"message": "Get http://127.0.0.1/server-status?auto: dial tcp 127.0.0.1:80: getsockopt: connection refused",
},
"metricset": {
"module": "apache",
"name": "status",
"rtt": 1082
},
.
.
.
"type": "metricsets"