- Heartbeat Reference: other versions:
- Overview
- Contributing to Beats
- Getting Started With Heartbeat
- Setting up and running Heartbeat
- Configuring Heartbeat
- Set up Heartbeat monitors
- Specify general settings
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and Enhance the exported data
- Parse data by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- heartbeat.reference.yml
- Exported fields
- Monitoring Heartbeat
- Securing Heartbeat
- Troubleshooting
WARNING: Version 6.2 of Heartbeat 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.
Common heartbeat monitor fields
editCommon heartbeat monitor fields
editNone
monitor fields
editCommon monitor fields.
monitor.type
edittype: keyword
The monitor type.
monitor.name
edittype: keyword
The monitors configured name
monitor.id
edittype: keyword
The monitors full job ID as used by heartbeat.
duration fields
editTotal monitoring test duration
monitor.duration.us
edittype: long
Duration in microseconds
monitor.scheme
edittype: keyword
Address url scheme. For example tcp, tls, http, and https.
monitor.host
edittype: keyword
Hostname of service being monitored. Can be missing, if service is monitored by IP.
monitor.ip
edittype: ip
IP of service being monitored. If service is monitored by hostname, the ip field contains the resolved ip address for the current host.
monitor.status
edittype: keyword
required: True
Indicator if monitor could validate the service to be available.
On this page