What is a Server HTTP Web Trace?
Technological, organizational or cultural environments have evolved with the rise of microservices, containerized apps, different programming languages, dependencies. Monitoring products relying on logs or "trace profiling" cannot face production application increasing complexity and massive amount log or trace to analyze. Application architecture and code shifts over the different network hops and layers making it hard for DevOps and Production engineers to grasp at a precise and standardized application performance host visibility, especially in the case of ephemeral instances and underlying infrastructure.
Despite language, framework or application topology changes, the network layer remains the fundamental layer on which applications converge upon, regardless of an application's complexity and heterogeneous stack.
With this in mind, ServicePilot has designed a server HTTP remote capture solution, or called Web Trace, to capture HTTP traffic statistics on interfaces and ports listened. As a result, the ServicePilot Web Trace package and its agent can be installed, providing site reliability engineers immediate APM value without any changes to the application code and HTTP business transaction analysis.
Web Trace package description
This package monitors HTTP transactions.
This package uses a ServicePilot Agent and a pcap network capture library to capture HTTP traffic statistics seen on interfaces and ports listed.
HTTP statistics gathered include:
- Counts of HTTP response codes
- Counts of HTTP request types
- Counts of established and timed-out transactions
- Average response time
- Counts of transaction response times
Note that this web probe does not handle encrypted HTTPS traffic.
HTTP trace, or server web remote capture, is no silver bullet, local bandwidth utilization is higher because network transactions are analyzed in real-time, however, when compared to code-level APM agents, the agent capture consumption of CPU load and memory utilization are negligible.
Also note that WinPcap cannot capture traffic on Windows loopback interfaces.