On 15/09/21 7:04 am, Moti Berger wrote:
Hi
I have the followings in squid.conf:
logformat metrics %icap::tt %adapt::all_trs %adapt::sum_trs
%{service_req_a}adapt::sum_trs %{service_resp_a}adapt::sum_trs
%{service_req_b}adapt::sum_trs %{service_resp_b}adapt::sum_trs
access_log daemon:/var/log/squid/metrics.log metrics
icap_service service_req_a reqmod_precache bypass=1 on-overload=wait
routing=1 icap://a.y:12345/request
icap_service service_req_b reqmod_precache bypass=1 on-overload=wait
icap://b.y:10101/request
adaptation_service_chain svcRequest service_req_a service_req_b
adaptation_access svcRequest deny manager
adaptation_access svcRequest allow all
icap_service service_resp_a respmod_precache bypass=1
on-overload=wait routing=1 icap://a.y:12345/response
icap_service service_resp_b respmod_precache bypass=1
on-overload=wait icap://b.y:10101/response
adaptation_service_chain svcResponse service_resp_a service_resp_b
adaptation_access svcResponse deny manager
adaptation_access svcResponse allow all
I see in metrics.log lines like this:
4 4,180 4,180 4 180 - -
Now I wonder how come the value of %icap:tt isn't at least as the sum of
all the numbers appear on %adapt::all_trs or %adapt::sum_trs (assuming
no failed transactions)?
%icap:: codes are relevant to ICAP.
%adapt:: codes are relevant to all adaptation types: ICAP, eCAP, and (in
theory, though often not really) redirector and URL re-writer helpers.
NP: failed transactions timers are included in all three metrics.
If %icap:tt isn't at least the sum of all ICAPs processing time, what is?
AFAIK you are right - it is supposed to be the sum of all processing
time for ICAP related things.
It does seem to be a bit odd that only the first one ("4") is counted.
Likely a bug IMO.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
