- Heartbeat Reference: other versions:
- Heartbeat overview
- Quick start: installation and configuration
- Set up and run
- Configure
- Monitors
- Task scheduler
- General settings
- Project paths
- Output
- Kerberos
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Processors
- Define processors
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- rate_limit
- registered_domain
- rename
- script
- syslog
- translate_sid
- truncate_fields
- urldecode
- Autodiscover
- Internal queue
- Logging
- HTTP endpoint
- Regular expression support
- Instrumentation
- heartbeat.reference.yml
- How to guides
- Exported fields
- Beat fields
- Synthetics browser metrics fields
- Cloud provider metadata fields
- Common heartbeat monitor fields
- Docker fields
- ECS fields
- Host fields
- HTTP monitor fields
- ICMP fields
- Jolokia Discovery autodiscover provider fields
- Kubernetes fields
- Process fields
- Host lookup fields
- APM Service fields
- SOCKS5 proxy fields
- Monitor summary fields
- Synthetics types fields
- TCP layer fields
- TLS encryption layer fields
- Monitor
- Secure
- Troubleshoot
- Get help
- Debug
- Common problems
- Heartbeat uses too much bandwidth
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- Publishing to Logstash fails with "connection reset by peer" message
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
- High RSS memory usage due to MADV settings
- Contribute to Beats
None
HTTP related fields.
-
http.url
-
Service url used by monitor.
type: alias
alias to: url.full
-
http.response.body.hash
-
Hash of the full response body. Can be used to group responses with identical hashes.
type: keyword
-
http.response.redirects
-
List of redirects followed to arrive at final content. Last item on the list is the URL for which body content is shown.
type: keyword
-
http.response.headers.*
-
The canonical headers of the monitored HTTP response.
type: object
Object is not enabled.
HTTP layer round trip times.
Duration between first byte of HTTP request being written and response being processed by validator. Duration based on already available network connection.
Note: if validator is not reading body or only a prefix, this number does not fully represent the total time needed to read the body.
-
http.rtt.validate.us
-
Duration in microseconds
type: long
Duration of validator required to read and validate the response body.
Note: if validator is not reading body or only a prefix, this number does not fully represent the total time needed to read the body.
-
http.rtt.validate_body.us
-
Duration in microseconds
type: long
Duration of sending the complete HTTP request. Duration based on already available network connection.
-
http.rtt.write_request.us
-
Duration in microseconds
type: long
Time required between sending the start of sending the HTTP request and first byte from HTTP response being read. Duration based on already available network connection.
-
http.rtt.response_header.us
-
Duration in microseconds
type: long
-
http.rtt.content.us
-
Time required to retrieved the content in micro seconds.
type: long
Duration required to process the HTTP transaction. Starts with the initial TCP connection attempt. Ends with after validator did check the response.
Note: if validator is not reading body or only a prefix, this number does not fully represent the total time needed.
-
http.rtt.total.us
-
Duration in microseconds
type: long