浏览代码

modules: readme files regenerated - statsc ... [skip ci]

Kamailio Dev 8 年之前
父节点
当前提交
6a69220ec8
共有 3 个文件被更改,包括 12 次插入11 次删除
  1. 4 4
      src/modules/statsc/README
  2. 7 6
      src/modules/statsd/README
  3. 1 1
      src/modules/usrloc/README

+ 4 - 4
src/modules/statsc/README

@@ -31,7 +31,7 @@ Daniel-Constantin Mierla
 
         4. RPC Commands
 
-              4.1. statsc.exec
+              4.1. statsc.report
 
    List of Examples
 
@@ -57,7 +57,7 @@ Chapter 1. Admin Guide
 
    4. RPC Commands
 
-        4.1. statsc.exec
+        4.1. statsc.report
 
 1. Overview
 
@@ -135,9 +135,9 @@ modparam("statsc", "track", "req.received=rcv_requests;rpl.received=rcv_replies"
 
 4. RPC Commands
 
-   4.1. statsc.exec
+   4.1. statsc.report
 
-4.1.  statsc.exec
+4.1.  statsc.report
 
    Get the report of recorded statistics.
 

+ 7 - 6
src/modules/statsd/README

@@ -129,11 +129,10 @@ failure_route[tryagain] {
 3.2.  statsd_gauge(key, value)
 
    Gauges are a constant data type. They are not subject to averaging and
-   they don’t change unless you change them. That is, once you set a
-   gauge value, it will be a flat line on the graph until you change it
-   again.
+   they don't change unless you change them. That is, once you set a gauge
+   value, it will be a flat line on the graph until you change it again.
 
-   Gauges are useful for things that are already averaged, or don’t need
+   Gauges are useful for things that are already averaged, or don't need
    to reset periodically
 
    This function can be used in ALL ROUTES.
@@ -141,10 +140,12 @@ failure_route[tryagain] {
    The statsd server collects gauges under the stats.gauges prefix.
 
    Example 1.4. statsd_set usage
+...
 route [gauge_method]{
     statsd_gauge("method"+$rm, "+1");
     statsd_gauge("customer_credit"+$var(customer),"$var(customer_credit)");
 }
+...
 
 3.3.  statsd_start(key)
 
@@ -158,7 +159,7 @@ route [gauge_method]{
    The statsd server collects all timers under the stats.timers prefix and
    will calculate the lower bound, mean, 90th percentile, upper bound, and
    count of each timer for each period (by the time it can be seen in
-   graphite, that’s usually per minute).
+   graphite, that's usually per minute).
 
    Example 1.5. statsd_start usage
 ...
@@ -205,6 +206,6 @@ if(geoip_match("$si", "src")){
 ...
 if (t_check_status("408")) {
     statsd_decr("kamailio.successfulCalls");
-    statsd_incr("kamailio.reply.busy");
+    statsd_incr("kamailio.reply.timeout");
 }
 ...

+ 1 - 1
src/modules/usrloc/README

@@ -895,7 +895,7 @@ modparam("usrloc", "close_expired_tcp", 1)
 
    If set to 1, Kamailio expects to deal with BIGINT type on database
    columns for expires and last modified values. It allows to handle
-   better the daylight time adjustmens. If set to 0, those columns are
+   better the daylight time adjustments. If set to 0, those columns are
    expected to be on default type 'DATETIME'. When it is 1, the database
    columns types have to be changed manually to 'BIGINT'.