Splunk Completes Acquisition of Plumbr Learn more

HTTP Requests

Plumbr Universal Agent monitors outgoing HTTP/1.0 and HTTP/1.1 requests made while handling an API call. These are detected by analyzing network traffic. Detecting outgoing HTTPS (SSL/TLS) requests is supported if the library used to make the requests uses OpenSSL for handling TLS.

The agent collects the request URL, request method and response code for each request. If the TCP connection is closed before request handling is finished, the request is marked as aborted, which is shown instead of the response code. The request duration is the time between when the first byte of the request was written by the application and when the last byte of the response was received. In case this was the first request for the same TCP connection, the time to open the connection is also included.

Each individual request longer than the bottleneck threshold (1 second) is registered as a bottleneck. If the combined duration of all requests below the bottleneck threshold in the same API call is longer than the threshold, then a multiple requests bottleneck is registered. HTTP request bottlenecks are not registered if the target is also monitored by either the Universal or Java agent. In that case bottlenecks from that target will be present instead.