- Heartbeat Reference: other versions:
- Overview
- Getting Started With Heartbeat
- Setting up and running Heartbeat
- Configuring Heartbeat
- Set up 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
- Contributing to Beats
This functionality is in beta and is subject to change. The design and
code is considered to be less mature than official GA features. Elastic will
take a best effort approach to fix any issues, but beta features are not
subject to the support SLA of official GA features.
Common heartbeat monitor fields
editCommon heartbeat monitor fields
editNone
monitor fields
editCommon monitor fields.
-
monitor.type -
type: keyword
The monitor type.
-
monitor.name -
type: keyword
The monitors configured name
-
monitor.id -
type: keyword
The monitors full job ID as used by heartbeat.
duration fields
editTotal monitoring test duration
-
monitor.duration.us -
type: long
Duration in microseconds
-
monitor.scheme -
type: keyword
Address url scheme. For example
tcp,tls,http, andhttps. -
monitor.host -
type: keyword
Hostname of service being monitored. Can be missing, if service is monitored by IP.
-
monitor.ip -
type: ip
IP of service being monitored. If service is monitored by hostname, the
ipfield contains the resolved ip address for the current host. -
monitor.status -
type: keyword
required: True
Indicator if monitor could validate the service to be available.
On this page
Was this helpful?
Thank you for your feedback.