- Heartbeat Reference: other versions:
- Overview
- Getting Started With Heartbeat
- Setting up and running Heartbeat
- Configuring Heartbeat
- Set up monitors
- Specify general settings
- Specify Observer and Geo Options
- Configure the internal queue
- Configure the output
- Configure index lifecycle management
- Specify SSL settings
- Filter and Enhance the exported data
- Define processors
- Add cloud metadata
- Add fields
- Add labels
- Add the local time zone
- Add tags
- Decode JSON fields
- Decode Base64 fields
- Decompress gzip fields
- Community ID Network Flow Hash
- Convert
- Drop events
- Drop fields from events
- Extract array
- Keep fields from events
- Registered Domain
- Rename fields from events
- Add Kubernetes metadata
- Add Docker metadata
- Add Host metadata
- Add Observer metadata
- Dissect strings
- DNS Reverse Lookup
- Add process metadata
- Parse data by using ingest node
- Enrich events with geoIP information
- Configure project paths
- Configure the Kibana endpoint
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- Autodiscover
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- heartbeat.reference.yml
- Exported fields
- Beat 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
- SOCKS5 proxy fields
- Monitor summary fields
- TCP layer fields
- TLS encryption layer fields
- Monitoring Heartbeat
- Securing Heartbeat
- Troubleshooting
- Contributing to Beats
HTTP monitor fields
editHTTP monitor fields
editNone
http
editHTTP 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
rtt
editHTTP layer round trip times.
validate
editDuration 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
validate_body
editDuration 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
write_request
editDuration of sending the complete HTTP request. Duration based on already available network connection.
-
http.rtt.write_request.us -
Duration in microseconds
type: long
response_header
editTime 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
total
editDuration 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