Common heartbeat monitor fields
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
None
Common monitor fields.
monitor.type-
The monitor type.
type: keyword
monitor.name-
The monitors configured name
type: keyword
monitor.name.text- type: text
monitor.id-
The monitors full job ID as used by heartbeat.
type: keyword
monitor.id.text- type: text
Total monitoring test duration
monitor.duration.us-
Duration in microseconds
type: long
monitor.scheme-
Address url scheme. For example
tcp,tls,http, andhttps.type: alias
alias to: url.scheme
monitor.host-
Hostname of service being monitored. Can be missing, if service is monitored by IP.
type: alias
alias to: url.domain
monitor.ip-
IP of service being monitored. If service is monitored by hostname, the
ipfield contains the resolved ip address for the current host.type: ip
monitor.status-
Indicator if monitor could validate the service to be available.
type: keyword
required: True
monitor.check_group-
A token unique to a simultaneously invoked group of checks as in the case where multiple IPs are checked for a single DNS entry.
type: keyword
monitor.timespan-
Time range this ping reported starting at the instant the check was started, ending at the start of the next scheduled check.
type: date_range
monitor.origin-
The origin of this monitor configuration, usually either "ui", or "project"
type: keyword
Project info for this monitor
monitor.project.id-
Project ID
type: keyword
monitor.project.name-
Project name
type: keyword