Ricardo asked:

In particular is there a way to see the statistics related to the "load" of the server? Or cpu used by kamailio?

Hi,

"kamctl fifo get_statistics all" will show you all available statistics, for a more simpler view try "kamctl moni". The closest thing you'll find regards to the load are inuse transaction, or concurrent dialogs.

The CPU used from kamailio can be seen by normal system tools like top.

Regards,

Henning

On 2/27/11 5:27 AM, Juha Heinanen wrote:

Henning Westerholt writes:

...

"kamctl fifo get_statistics all" will show you all available statistics, for a more simpler view try "kamctl moni". The closest thing you'll find regards to the load are inuse transaction, or concurrent dialogs.

tmx:inuse_transactions would be more useful if it would contain an average over some time (1-5 minutes or something like the routers have) rather than an instantaneous value. but last time when i looked, it was difficult to implement in k any kind of stat with average value. perhaps that has now changed with sip router?

What I used, even in older versions, is to combine statistics with rtimer and htable. The statistics were just simple counters, holding integer value, incremented/decremented as wanted.

There are some stats that just increment, practically counting different events.

Here is what I do if I want to get like "load" stats - i.e., number of events in a specific period of time. For example number of 2xx transactions per minute:

Load htable module and define a htable, say stats.

In event_route[htable:mod-init] I set $sht(stats=>2xx_transactions) = 0;

Load rtimer module to execute a route block every minute. In that route block, do this kind of logic:

$var(stats) = $stat(2xx_transactions); $var(diff) = $var(stats) - $sht(stats=>2xx_transactions); $sht(stats=>2xx_transactions) = $var(stats);

- insert in db the value of $var(diff) along with the timestamp so you have the number of transactions answered with 2xx during the last minute. Then configure siremis to make a graph out of the db records

You can have another rtimer route executed not that often that can delete records older than 1-2 days, so you don't fill up the database.

Cheers, Daniel

tmx:2xx_transactions

Daniel-Constantin Mierla writes:

Here is what I do if I want to get like "load" stats - i.e., number of events in a specific period of time. For example number of 2xx transactions per minute:

Load htable module and define a htable, say stats.

In event_route[htable:mod-init] I set $sht(stats=>2xx_transactions) = 0;

i'm coming back to this rather old thread. my question is, what is the benefit (if any) of using htable to store the stats as opposed to shared variables ($shv instead of $sht)?

-- juha

Daniel-Constantin Mierla writes:

...

i'm coming back to this rather old thread. my question is, what is the benefit (if any) of using htable to store the stats as opposed to shared variables ($shv instead of $sht)?

the benefit of using htable is dynamic name for keys, otherwise the shared variables are faster to access.

daniel,

thanks for your answer. in case of statistics, the names are known in advance, so perhaps for them shared variables would be the best choice.

-- juha

regarding tmx:inuse_transactions stat, it does not seem to exist among tm.stats:

# sip-proxy_ctl tm.stats { current: 0 waiting: 0 total: 8 total_local: 0 replied_locally: 2 6xx: 0 5xx: 0 4xx: 1 3xx: 0 2xx: 7 created: 8 freed: 8 delayed_free: 0 }

or does it have the same value as created - freed?

-- juha

Hi Juha,

On 3/1/11 9:34 AM, Juha Heinanen wrote:

Juha Heinanen writes:

...

regarding tmx:inuse_transactions stat, it does not seem to exist among tm.stats:

...

...

or does it have the same value as created - freed?

a took a look at the code and tmx inuse_transactions seems to be equal to tm current transactions.

you are right, I saw your email but I forgot to answer it. SER core, sl & tm exported more stats in regard to transactions and replies, so I kept that version when we integrated and exported them via K stats API.

Cheers, Daniel