New

The executive guide to generative AI

Read more
About usPartnersSupport|Login

WARNING: Version 5.4 of Metricbeat has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Event Structure Key Metricbeat Features »
Elastic Docs ›Metricbeat Reference [5.4] ›How Metricbeat Works

Error Event Structure

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Error Event Structure

edit

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": "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"
« Event Structure Key Metricbeat Features »
Was this helpful?
Feedback