Application trace monitoring
How to monitor WEBTRACE?

ServicePilot apptrace-webtrace

What is a Server HTTP Web Trace?

HTTP protocol is critical to many organizations. Wether using SOAP over HTTP service links, external HTTP calls aornd relying on internal HTTP web applications, HTTP traffic capture and statistics on any local server becomes handy when you server handles network traffic for multiple applications, going though different stacks and with different architectures or micro-services.

ServicePilot provides a server HTTP Web Trace package, called Web Trace, to capture local server HTTP traffic statistics on the server interfaces and ports we listen on. 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 monitoring

This package monitors HTTP transactions.

This package uses a ServicePilot Agent 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 ServicePilot Windows Agent cannot capture traffic on Windows loopback interfaces.

Application trace monitoring WEBTRACE 0

Application trace monitoring WEBTRACE 1

Application trace monitoring WEBTRACE 2

Application trace monitoring WEBTRACE 3

Other Application Traces integrations