HTTP 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
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