Overview

Network monitoring is an invaluable feature that lies at the heart of modern IT infrastructure management. With network monitoring in place, you can proactively identify and address potential issues before they escalate into critical problems, ensuring uninterrupted operations and minimizing downtime.

This feature empowers IT teams with real-time visibility into network traffic, latency, bandwidth utilization, etc., enabling them to make informed decisions swiftly.

Server-Timing

Measuring request durations on the client has many advantages over doing it on the server. Durations measured from client's perspective include total roundtrip of the request, this involves time spent on DNS lookups, SSL connection negotiation etc.

When monitoring and analyzing network performance, there is one small thing that you can do on the server in order to greatly improve the value you get from analyzing request durations.

Using Server-Timing header, you can enrich Appelium network performance metrics with a very valuable piece of information - the time the request took to process on the server. This is a standard response header, defined by W3C and chances are your application server or a proxy already includes it in all responses. If not, it is quite straight forward to integrate it. Here is an example of how it can looks like:

Server-Timing: total;dur=100.2

This simple format with total segment, is recognized by Appelium SDKs and will enable you to gain even more insights into network performance of your system.

Note

Appelium expects the unit for duration to be ms. This unit is also recommended by W3C.

Note that the header can include more information in it's extended form, but these details are not needed nor used by Appelium:

Server-Timing: db;dur=53, app;dur=47.2, total;dur=100.2