And to have a complete picture of the Web service, we have introduced the workload management concept inside Kronometrix to gather and report data from one or many data sources and bound those to a SLA for upper management reporting. Nice and easy.
Some first development snapshots from our implementation. Let's first switch to night mode, it is 23:10 here in Finland. So, here you go:
All requests dashboard
This shows a number of HTTP requests gathered as a stream graph, over time.
|All requests as a stream|
|Instant response time|
Simple to see all requests as a continuous stream of data over time
A simple break down reporting the following metrics:
#01 timestamp : seconds since Epoch, time #02 request : the HTTP request name #03 ttime : total time, entire operation lasted, seconds #04 ctime : connect time it took from the start until the TCP connect to the remote host (or proxy) was completed, seconds #05 dnstime : namelookup time, it took from the start until the name resolving was completed, seconds #06 ptime : protocol time, it took from the start until the file transfer was just about to begin, seconds #07 pktime : first packet time, it took from the start until the first byte was just about to be transferred, seconds #08 size : page size, the total amount of bytes that were downloaded #09 status : response status code, the numerical response code that was found in the last retrieved HTTP(S) transfer
looking like this:
|Per-request response time|
Easy to break down at the request level, including outliers
Close to these dashboards are the operating system metrics, to have a complete picture of the running system. Later we will show how we define and report combined all resources as a complete workload. Stay tuned and join our discussion group, here
We are the makers of Kronometrix, come and join us !