Hi Jonathan,
No I don't think there is any issue when saving these stats, So I think
this is a bug itself which needs to be fixed ?
# while true; do echo 'show stat' | socat -
UNIX-CLIENT:/var/run/haproxy.sock | grep BACKEND | cut -d , -f 2,41;
sleep 1; done
BACKEND,15325469
BACKEND,15325511
BACKEND,14387610
BACKEND,14387660
BACKEND,13854344
BACKEND,14387745
BACKEND,13854440
BACKEND,15045037
BACKEND,15045086
BACKEND,15325845
BACKEND,15325895
BACKEND,14388003
On Friday 14 June 2013 11:28:15 PM IST, Jonathan Matthews wrote:
On 14 June 2013 10:10, Ashish Jaiswal <[email protected]> wrote:
HI Jonathan,
You mean to say that the hrsp_2xx will always increment. But it doesn't
seems to be as the value are always floating.
My major concern is how will one manage to see that how many client are
getting and 3xx/2xx code when they are getting served.
The "show stat" can be looked up as many time we want. Is there any way
where we can be sure that the show stat is showing the stat from last last 5
min or 1 min or what ever elapsed time.
But it is becoming difficult to understand this. since I'm not sure how many
clients has got served 2xx during the particular time.
epoch 2xx
3xx 4xx 5xx
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198785:45511301:98:26038:31575275:13471396:363095:100026:0:0:79:0:79789
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198795:42791104:67:24597:29708693:12645578:339827:95649:0:0:70:0:74804
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198806:42791857:67:24597:29709185:12645831:339837:95649:0:0:69:0:74804
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198816:41279933:77:23783:28669637:12186636:327477:94791:0:0:82:0:71402
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198826:42793399:67:24597:29710228:12646304:339855:95650:0:0:68:0:74804
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198836:42434557:62:24019:29566746:12441335:333463:91580:0:0:68:0:74536
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198846:42946664:67:24746:29825328:12683434:340971:95572:0:0:82:0:74749
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198856:42436066:62:24019:29567729:12441842:333486:91583:0:0:68:0:74536
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198866:42796417:67:24600:29712213:12647285:339903:95658:0:0:74:0:74804
PUTVAL test.example.com/haproxy/haproxy_backend-example
1371198876:41230675:69:23321:28667585:12141642:327160:92959:0:0:71:0:71350
I don't know how you produced that, as it doesn't seem to be in a
format that HAProxy produces. (I may be wrong here, of course!)
May I suggest you examine the raw stats in their CSV format? There may
be an error creeping in to your CSV->Data transform stage.
Jonathan
--
- Ashish
