27 Mar
2012
27 Mar
'12
3:14 a.m.
On 3/26/12 4:27 PM, Klaus Darilion wrote:
On 26.03.2012 09:54, Daniel-Constantin Mierla wrote:
For some queries, it will be quite
long, e.g., presence queries with xml
docs. The purpose was to identify the query, the length can be adjusted
in the log command very easy in the code if people prefer longer output.
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/
Module: sip-router
Branch: master
Commit: 930aba2973c19370a5d50aac2661be66e9aacbc3
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=930aba2…
Author: Daniel-Constantin Mierla<miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla<miconda(a)gmail.com>
Date: Sun Mar 25 13:39:20 2012 +0200
core: new parameters to control and alert on time consuming ops
- latency_log - log level to print the messages related to latency
- latency_limit_db - limit of latency in ms for db operations. If a db
operation executed via DB API v1 takes longer that its value, a
message is printed in the logs, showing the first 50 characters of
the
db query
Why not the whole query? Would help debugging.